A large batch of x86 platform driver changes has been accumulating in the staging trees ahead of the upcoming mainline merge window, according to Phoronix, with the work expected to land in the next kernel release. The queue spans platform-level driver improvements aimed at laptops and the growing category of Windows-shipping gaming handhelds that users are increasingly re-imaging with Linux. (The specific target version identifier — reported as 7.4 — should be treated as provisional until the work is formally pulled; staging queues can shift before merge.)
The timing is familiar to anyone who follows kernel development: driver maintainers collect device-specific quirks, ACPI fixes, and embedded-controller interactions across a release cycle, then push them upstream during the merge window. What makes this batch noteworthy is its concentration on exactly the hardware categories where out-of-the-box Linux support has historically been weakest — thin-and-light laptops with vendor-custom ACPI tables, and handheld consoles whose button arrays, touchpads, and thermal profiles depend on platform drivers that upstream historically neglected in favour of desktop motherboard support.
For Hong Kong buyers, the practical implications are straightforward. Gaming handhelds and Linux-capable laptops are both widely sold through Hong Kong retailers and parallel-import channels, and the hardware classes this driver batch addresses are the ones Linux users most frequently report friction with: firmware quirks that break suspend-to-RAM, thermal sensors that don't report correctly, accelerometer and lid-switch events that don't fire, and keyboard or controller input that only works under the vendor's Windows-oriented kernel modules.
What upstream coverage actually changes
It is worth drawing a distinction that matters at the point of purchase. Many laptop and handheld vendors ship their own downstream kernel trees, patched to make their hardware function. Those vendor kernels tend to lag mainline by several releases, receive updates sporadically, and are effectively abandoned once a product leaves its sales window. Upstream driver coverage in mainline is the durable path: once a quirk or platform driver lands there, every distribution inherits it on its normal cadence, and support does not evaporate when the vendor moves on to the next model.
For a buyer comparing devices, this means the question is not "does Linux work on this laptop today?" but "does mainline support this laptop today, and does my distribution's kernel already carry it?"
A compatibility checklist for local buyers
Before buying a Linux-capable laptop or gaming handheld in Hong Kong, consider the following:
- Check your distribution's kernel version, not mainline's. Distros such as Fedora, Ubuntu, and Arch each track mainline at different speeds. A fix merged upstream may take weeks or months to reach a stable release branch.
- Verify upstream coverage of the fiddly subsystems. Touchscreen, Wi-Fi, and fingerprint reader support are the three most common gaps on otherwise well-supported laptops. Search the distribution's bug tracker and the kernel's device tree or DMI quirk lists before committing.
- Look for a vendor kernel tree with a published cadence. If you are buying at the bleeding edge, a vendor with an actively maintained downstream kernel is a safety net — but treat it as a bridge to upstream support, not a substitute.
- Read per-model community reports on battery life, sleep behaviour, and thermals. These platform-level behaviours are the last to stabilise and rarely appear in spec sheets or general reviews.
Merge window timing
The queued work is expected to be proposed for pull when the next merge window opens, following the usual release cadence — though "queued" is not "merged": work in a staging tree can still be held back, split, or revised before it reaches Linus's tree. Buyers weighing a purchase in the coming months may find it worth checking which kernel version their distribution is tracking and whether the hardware they want is already covered — or whether it is landing in the kernel just upstream of what they run today.
據 Phoronix 報道，一大批 x86 平台驅動程序的改動已在 staging trees 中積累，為即將到來的主線 merge window 作準備，預計將納入下一個核心版本。這批改動涵蓋針對手提電腦，以及日益壯大的 Windows 原裝遊戲掌機類別的平台層面驅動程序改善——不少用戶已將這些掌機重新安裝 Linux 系統。（有關目標版本編號——報道稱為 7.4——在改動正式 pull 之前應視為暫定，staging queues 在 merge 前仍可能變動。）
對於熟悉核心開發流程的人來說，這個時間安排並不陌生：驅動程序維護者在整個 release cycle 中收集各型號設備的 quirks、ACPI 修復及 embedded controller 互動問題，然後在 merge window 期間向上游推送。這批改動值得關注之處，在於它集中處理的正是 Linux 開箱支援一直最為薄弱的硬件類別——配備廠商自訂 ACPI 表格的輕薄手提電腦，以及其按鍵陣列、touchpad 及散熱配置均依賴平台驅動程序的掌機主機，而上游一直以來為優先支援桌面主機板而忽略這些驅動。
對香港買家而言，實際影響相當直接。遊戲掌機及可運行 Linux 的手提電腦在香港零售商及水貨渠道均有廣泛售賣，而這批驅動針對的硬件類別，正是 Linux 用戶最常反映出現問題的範疇：導致 suspend-to-RAM 失靈的 firmware quirks、無法正確回報的散熱感應器、沒有觸發的 accelerometer 及 lid-switch 事件，以及僅在廠商針對 Windows 的 kernel modules 下才能運作的鍵盤或手掣輸入。
上游支援覆蓋的實際意義
在購買決定上，有一個區別值得釐清。不少手提電腦及掌機廠商均提供自家的 downstream kernel trees，當中已加入令其硬件運作的補丁。這些廠商核心通常落後主線多個版本，更新時常斷時續，而且產品一旦過了銷售期便 effectively 被放棄。主線的上游驅動覆蓋才是長久之策：一旦某個 quirk 或平台驅動進入主線，所有發行版都會按其正常節奏採用，支援亦不會隨著廠商轉向下一個型號而消失。
對正在比較不同設備的買家來說，這意味著關鍵問題不是「這部手提電腦今日能否運作 Linux？」而是「主線今日是否支援這部手提電腦？以及我所用發行版的核心是否已包含相關支援？」
本地買家的兼容性 checklist
在香港購買可運行 Linux 的手提電腦或遊戲手掣之前，請考慮以下各點：
- 查看你所用發行版的核心版本，而非主線版本。 Fedora、Ubuntu 及 Arch 等發行版跟進主線的速度各不相同。一個已向上游 merge 的修復，可能需要數週甚至數月才會到達 stable release 分支。
- 確認上游對繁瑣 subsystem 的覆蓋情況。 觸摸屏、Wi-Fi 及指紋讀取器支援，是整體支援良好的手提電腦上最常見的三個缺口。在作出決定之前，先搜尋發行版的 bug tracker 以及核心的 device tree 或 DMI quirk 列表。
- 留意廠商核心樹是否有公布的更新節奏。 如果你購買的是最前沿的型號，擁有活躍維護的 downstream kernel 的廠商是一重保障——但應將其視為通往上游支援的過渡，而非替代方案。
- 查閱按型號劃分的社群報告，了解電池續航、睡眠行為及散熱表現。 這些平台層面的行為最遲才會穩定下來，而且很少出現在規格表或一般評測之中。
Merge window 時間表
排隊中的改動預計會在下一個 merge window 開啟時提出 pull，跟隨慣常的 release 節奏——不過「queued」並不等於「merged」：staging tree 中的工作在到達 Linus 的樹之前，仍可能被押後、拆分或修訂。考慮在未來數個月內購買設備的買家，或會認為值得先查核發行版正在跟蹤哪個核心版本，以及心儀的硬件是否已獲支援——抑或正納入緊接其現行版本之後的核心之中。