Device descriptions let the kernel identify hardware. They do not implement every driver that a usable laptop or desktop needs.
What the merged tag contains
The Apple SoC device-tree merge includes initial M3 Pro, Max and Ultra descriptions with CPU, interrupt, power-state, serial, I2C and boot-framebuffer support. It also adds M1/M2 hardware-monitoring descriptions. A boot framebuffer provides a display path; it does not establish an accelerated GPU driver.
The distinction matters because a visible desktop can render through a different path from the one an application needs for demanding graphics. “There is an image” and “the GPU implements the required API” are separate observations.
Read the matrix by chip and device
The Asahi M3 support table, checked September 8, lists the base M3 GPU as WIP and the Pro/Max/Ultra GPU entries as TBA. The MacBook installer is WIP. Several Mac Studio entries differ from the laptop, including storage and networking status. The earlier recommendation to treat the whole M3 family as a routine daily-use Asahi installation was therefore too broad.
The table defines WIP as not ready for wider testing or distribution; TBA means active work is not being undertaken at that time. A linux-asahi entry refers to the downstream implementation, not automatically the same feature in an unmodified upstream kernel.
Turn a support table into a decision
The cover separates three questions: does the hardware have a description, is the required driver implemented, and does the installation support the intended device? Each question needs an answer for the exact machine, not just “Apple Silicon.”
For a hypothetical laptop workflow, needing an external display, suspend and GPU compute makes those three functions decisive even if Wi-Fi and the keyboard work. For a test machine accessed over a network, the requirements may be different. Counting green cells gives each feature the same importance when the user’s workload does not.
Track the upstream tag and downstream matrix separately. The merge is meaningful progress, while the matrix remains the more useful starting point for deciding whether a specific Mac can run the workload you need today.
September 8: verify device-tree merge and Asahi feature matrix; remove unsupported M3 daily-driver advice and distinguish boot framebuffer from accelerated graphics.