What Glanda's Path Into Linux 7.5 Means for Distro Users
A new Glanda GPU driver has been queued for the mainline kernel, according to Phoronix, which reported this week that the drm-misc-next pull request carrying the driver was sent out to stock DRM-Next with new material until the Linux 7.5 merge window opens in late December. The driver is described as the most notable item in that batch.
Whether it ultimately merges is still an open question — but for anyone running a distribution rather than tracking patchwork, the more useful part of the story is not the driver itself. It is the delivery mechanism that mainline inclusion creates.
Why upstreaming matters more than the pull request
To understand why a single driver submission earns coverage, it helps to look at the alternative. Hardware support that lives outside the mainline kernel — as an out-of-tree module — pushes a recurring maintenance burden onto users and administrators: the module has to be rebuilt whenever the kernel is updated, it complicates Secure Boot signing schemes, and security fixes arrive on a separate track from ordinary kernel updates, frequently lagging behind.
Support that lands in the mainline kernel works the other way around. It ships through routine package updates, exactly like the rest of the kernel. There is no manual installation step, no DKMS build on first boot, no third-party repository to trust, and no packaging overhead for distribution maintainers who would otherwise have to carry the module themselves. Secure Boot configurations keep working without extra signing steps, and future fixes to the driver ride the normal update cadence. In practical terms, that is the difference between a vendor claiming support and an ISO actually delivering it.
What remains open
Two uncertainties temper the headline. First, queuing material in DRM-Next is not the same as merging it: kernel maintainers hold final say, and nothing is settled until the merge window closes. Second, a mainline driver is a necessary condition for a healthy hardware ecosystem, not a sufficient one. Whether Glanda GPUs reach users in volume — whether OEMs ship them, whether Mesa and userspace tooling catch up, whether the stack performs well in practice — is a separate question that kernel inclusion alone does not answer.
There is also a timing gap worth noting. A merge in late December would place the 7.5 release in early 2027, but LTS distributions will not pick it up immediately. Ubuntu LTS and enterprise-grade releases rebase on newer kernels on their own schedule, often many months or longer after a feature reaches mainline. Organisations planning hardware roadmaps around LTS images should therefore treat the merge window as a starting point, not a delivery date.
For IT professionals tracking hardware-support roadmaps, the useful signal is the merge window itself. The point at which material is queued into DRM-Next — here, the run-up to late December — is a leading indicator of which drivers will be broadly available, through nothing more exotic than a routine system update, in the releases that follow.
Source: Phoronix.
Glanda 進入 Linux 7.5 對發行版用戶意味著什麼
據 Phoronix 報道，一款新的 Glanda GPU 驅動已排入主線內核的佇列。該網站本週報道，載有此驅動的 drm-misc-next pull request 已提交至標準 DRM-Next，加入最新材料，直至十二月下旬 Linux 7.5 的 merge window 開啟。該驅動被形容為該批次中最值得注意的項目。
此驅動最終能否成功合併仍然未有定論——但對於使用發行版而非自行追蹤補丁的用戶而言，這則新聞較有用的部分並非驅動本身，而是主線收錄所帶來的交付機制。
為何 upstreaming 比 pull request 更為重要
要理解為何單一驅動提交值得報道，不妨先看看另一條路。存在於主線內核之外的硬件支持——以 out-of-tree module 的形式——會把持續的維護負擔轉嫁給用戶和管理員：內核每次更新都必須重新編譯該模塊，令 Secure Boot 簽名機制更為複雜，而安全性修復亦以獨立於一般內核更新的渠道推出，往往滯後。
落在主線內核中的支持則恰好相反。它隨例行軟件包更新一併推出，與內核其他部分完全相同。無需手動安裝步驟，首次開機時無需 DKMS 編譯，無需信任任何第三方軟件庫，亦不會為原本須自行承載該模塊的發行版維護者增添打包工作。Secure Boot 配置在毋須額外簽名步驟的情況下繼續運作，驅動日後的修復亦會跟隨正常的更新節奏。實際而言，這就是廠商聲稱提供支持，與 ISO 真正交付該支持之間的分別。
仍然未有定論之處
有兩項不確定性為這則頭條消息降溫。第一，在 DRM-Next 排入材料不等於合併：內核維護者擁有最終決定權，在 merge window 結束前一切仍未落實。第二，主線驅動是健康硬件生態的必要條件，但非充分條件。Glanda GPU 能否大量觸及用戶——OEM 是否會出貨、Mesa 和 userspace 工具鏈能否跟上、整個 stack 在實踐中表現是否良好——是另一個問題，單靠收錄進內核並不能回答。
此外，尚有一個時間差值得注意。十二月下旬的合併會令 7.5 版本於 2027 年初推出，但 LTS 發行版不會立即採用。Ubuntu LTS 及企業級版本會按自身時間表在較新的內核上重新建立基礎（rebase），通常在功能進入主線後數個月甚至更久才會跟上。因此，圍繞 LTS 鏡像規劃硬件路線圖的機構，應把 merge window 視為起點而非交付日期。
對於追蹤硬件支持路線圖的 IT 專業人員而言，有用的信號正是 merge window 本身。材料排入 DRM-Next 的時點——即此處十二月下旬前的這段準備期——是領先指標，預示哪些驅動將在隨後的版本中廣泛可用，而獲取方式不過是一次例行的系統更新，並無任何更複雜的手續。
資料來源：Phoronix。