Apple M5 arrives on Linux with basic support in the apple-soc/dt-7.5 branch
Apple M5 support is coming to Linux, but your business Mac is not ready
On November 14, 2026, Apple’s base M5 chip, identified as t8142, was queued for initial Linux support in the apple-soc/dt-7.5 branch. That puts the code on track for Linux 7.5, but it does not turn an M5 Mac into a dependable Linux workstation.
We would not buy an M5 Mac today expecting Linux to replace macOS. The current work is a starting point for developers, not a finished platform for a small business.
What the 10-patch series actually adds
The series contains 10 patches. Nine update device-tree bindings and related arm64 files. A device tree tells Linux what hardware exists, where it is, and how the kernel should communicate with it.
That sounds technical because it is. The practical meaning is simpler. Linux is learning the basic layout of the M5 system, including its processor cores, interrupt controller, watchdog, serial hardware, pin controllers, I2C connections, and a basic framebuffer.
The changes cover three machines: the 14-inch MacBook Pro, identified as apple,j704, the 13-inch MacBook Air, identified as apple,j813, and the 15-inch MacBook Air, identified as apple,j815. The MacBook Pro device tree has been boot-tested with macOS 26.6 firmware and the latest m1n1 bootloader. The Air models have device-tree entries, but practical testing is less clear.
Linux 7.5 is not the same as Linux-ready
Apple Silicon support has been arriving in small steps. Initial M3 support entered Linux 7.2. M4 support entered Linux 7.4. M5 is following the same path.
But each step has been narrow. The M5 work is described as minimal, and proper GPU support is not included. That matters more than the processor name on the box.
Without full graphics support, Linux is not ready for ordinary creative work, smooth multi-display use, video production, or other jobs that depend on the M5 GPU. The available display support is closer to a boot framebuffer than a complete desktop graphics stack. Other hardware support also remains incomplete, including items such as Wi-Fi, Bluetooth, the touchpad, battery reporting, the camera, speakers, and Touch ID.
For a business owner, this is the difference between “Linux can start” and “employees can work.” They are not the same thing.
What this means for a 30-person company
For most small and mid-sized businesses, this news changes nothing today. An M5 Mac running Linux should not be placed into regular service for accounting, sales, design, customer support, or executive work unless someone is prepared to troubleshoot hardware and software problems directly.
We would also avoid treating Linux 7.5 as a reason to delay a purchase or replace working Macs. If a department needs Linux, use hardware with mature Linux support. If the department needs an M5 Mac, keep macOS as the operating system and run Linux in a virtual machine where that fits the workload.
There is one sensible exception. A technical employee or developer may want an M5 system for testing Asahi Linux and upstream kernel work. That can be a useful project machine. It should not be sold internally as a supported employee endpoint.
What we would do with the IT budget
We would spend the money on tested hardware, backup coverage, endpoint protection, and a support plan before experimenting with M5 Linux. A failed webcam or missing Wi-Fi driver is an annoyance at home. In a business, it becomes a ticket, lost time, and sometimes a missed customer call.
We would also wait for two things before approving M5 Linux for production use: confirmation that the patches actually land in the final Linux 7.5 release, and evidence that the major hardware functions work reliably on each specific Mac model.
That first point is not settled yet. The code is queued and expected to enter Linux 7.5, but final inclusion is not confirmed. Even if it lands, the release will provide a foundation, not a finished desktop platform.
If you own an M5 Mac and want to test Linux, keep the device out of the company’s critical workflow, make a full backup, and use a spare machine or separate test account. If you need help deciding whether the experiment belongs in your business, IT911Now can review the hardware, software, and support risks before you spend money.