Apple's current-generation M4 and A18 Pro chips are set to receive formal description inside the mainline Linux kernel for the first time, after Asahi Linux developer Sven Peter posted a pull request series of Apple SoC device tree changes ahead of the Linux 7.4 merge window, according to Phoronix.
The series carries an initial device tree — the hardware description format Linux uses to tell the kernel what silicon and peripherals a given board actually contains — for systems built around the base M4 SoC, plus a second entry for what the pull request describes as the "MacBook Neo" built on the A18 Pro SoC. That designation appears only in the pull request's own wording. Apple has not announced any product by that name; it may function as an internal codename or placeholder rather than a confirmed device.
From custom kernel to standard kernel
The practical significance for anyone running Asahi Linux on M4-era Apple hardware is the shift from Asahi's own maintained kernel tree to the standard kernel shipped by every mainstream distribution. Today, Asahi users depend on a downstream, patched kernel to get their machines to boot and run. Once this material lands in 7.4, the M4 and A18 Pro device trees will be present in Fedora, Arch and Debian kernels regardless of whether the user runs Asahi downstream at all — a visible, checkable milestone even for people who never intend to switch distributions.
What it is — and what it isn't
The framing guardrail matters here, because merging device trees alone delivers far less than the milestone suggests. Approval does not mean a working desktop. The deeper work — Asahi's out-of-tree drivers, power management and GPU support — remains unfinished downstream, and the SoCs become formally acknowledged inside the kernel rather than genuinely supported on day one. Readers should not treat this as a green light to reimage their Macs once 7.4 releases.
The timing is nonetheless meaningful. Rather than deferring the series to a later window, Peter is targeting 7.4 while the merge window is open later this month, which signals maintainer confidence in the material's stability — a notable consideration given the volunteer bandwidth available for this kind of maintenance.
Why this matters beyond Asahi
Perhaps the more unusual development is indirect. Apple publishes essentially nothing about the internals of its own silicon. If these device trees are merged, they will become the most detailed publicly readable technical description of how an M4 or A18 Pro platform is wired — de facto open documentation for hardware that otherwise ships in a black box. That puts a kernel subsystem in the rare position of serving as a reference document, and it raises the ceiling for everything from emulation to secondary projects built on those platforms.
What to watch next
Three things will tell the community more than the merge itself. First, whether 7.4 actually lands as scheduled. Second, whether Apple says anything publicly that clarifies the "MacBook Neo" designation — a move that would reframe the second device tree as an actual shipping product. Third, and most relevant to end users, when Asahi's own installer images begin advertising M4 or A18 Pro support; that is the practical trigger for anyone waiting to test the hardware, and it will trail the mainline merge by some margin. Until then, the device trees are a milestone to track, not a reason to change workflows.
據 Phoronix 報道，Apple 現行世代的 M4 與 A18 Pro 晶片即將首次在 mainline Linux kernel 內獲得正式描述。Asahi Linux 開發者 Sven Peter 已在 Linux 7.4 的 merge window 開始前，發表了一系列關於 Apple SoC device tree 變更的 pull request。
這系列包含一份初步 device tree——即 Linux 用來告知 kernel 某塊板卡實際配備哪些晶片與周邊裝置的硬件描述格式——涵蓋以基礎版 M4 SoC 建立的系統，另有第二份條目對應 pull request 中所指、建基於 A18 Pro SoC 的「MacBook Neo」。該名稱僅出現於 pull request 的字面描述中。Apple 並未公佈任何以此為名的產品；它可能只是內部代號或佔位名稱，而非已確認的機款。
從自行維護的 kernel 到標準 kernel
對於在 M4 時代 Apple 硬件上運行 Asahi Linux 的人而言，實際意義在於從 Asahi 自行維護的 kernel tree 轉向各大主流發行版所採用的標準 kernel。現時，Asahi 用戶依賴一套下游修改版 kernel 才能使機器開機運行。一旦這批材料進入 7.4，M4 與 A18 Pro 的 device tree 將無差別地出現在 Fedora、Arch 及 Debian 的 kernel 中——即使使用者根本沒有執行 Asahi 下游版本。這對那些從未打算更換發行版的人而言，也是一個可見、可查證的里程碑。
它代表什麼——以及不代表什麼
此處的表述界定至關重要，因為單純合併 device tree 所帶來的進展，遠不及該里程碑聽起來那麼多。獲得批准並不等同於有可用的桌面環境。更深層的工作——Asahi 的 out-of-tree driver、電源管理及 GPU 支援——在下游仍未完成，各款 SoC 並非在 7.4 一推出當日即獲真正支援，只是在 kernel 內獲得了形式上的承認。讀者不應把這視為 7.4 發佈後重新安裝 Mac 的綠燈信號。
不過，時機本身仍有意義。Peter 沒有把這系列推遲至較後的 merge window，而是趁本月稍後 7.4 merge window 開啟期間鎖定 7.4 推進，這反映維護者對材料穩定性的信心——鑑於此類維護工作可用的志願者精力有限，這一點尤為值得注意。
為何這對 Asahi 以外的範疇同樣重要
或許較不尋常的發展是間接性的。Apple 幾乎從不公開自家晶片的內部結構。若這批 device tree 得以合併，它們將成為對 M4 或 A18 Pro 平台硬件連接方式最詳盡的公開技術描述——對於一款原本只以「黑盒子」形式出貨的硬件而言，這將成為事實上的公開文件。這使 kernel 某個子系統罕有地成為參考文獻，並為由模擬器到建基於這些平台的次級專案等一切工作，提升其發展上限。
接下來值得觀察的事項
有三件事比 merge 本身更能向社群說明走勢。第一，7.4 是否如期推出。第二，Apple 會否就「MacBook Neo」的命名公開表態——若然，將把第二份 device tree 重新定位為實際出貨的產品。第三，亦與最終用戶最相關的，是 Asahi 自家的安裝映像何時開始標示支援 M4 或 A18 Pro——這是任何等待測試該硬件的人所關心的實際觸發點，而它將較 mainline 合併晚一段時間。在那之前，device tree 是值得追蹤的里程碑，而非改變工作流程的理由。