First Thunderbolt and USB4 controller for M1–M3: what it means and how to check it

Quick answer: yes, there is a driver sent to the kernel list; it was signed by Sven Peter and is intended to enable support for Thunderbolt and USB4 on M1, M2, and M3 chips. According to the announcement on the Asahi project mailing list, the patch is the result of years of reverse engineering without Apple’s collaboration and represents the first driver of this kind sent for review for these chips.

The news broke following the patch submission to the kernel mailing list. The code still needs to pass the review of the kernel maintainers; meanwhile, the patch is a proof of concept that could solve one of the most requested absences for Apple Silicon users running Linux.

What is this driver and why does it matter?

Why should this concern me?

Because if integrated, the driver will unify management of the physical port shared by Thunderbolt and USB4, which can unlock peripherals at the speeds they require. This matters especially to those working with large volumes of data or external displays from Linux on Mac.

What does the patch technically do?

In plain words: the patch reconstructs the behavior of the controller that Apple does not document, coordinating the physical part of the port (shared electronics) with the kernel’s USB subsystem to manage links, power, and devices. This explains why the project required so much prior investigation.

How to test and enable support (for advanced users)

How can I get and test the patch?

Short answer: get the email or the one circulated on the kernel mailing list and apply it to your local kernel tree before compiling and testing on a test machine.

As a general guide (not a literal command list nor including specific repository commands):

• Subscribe to the kernel mailing list to find the original message from Sven Peter.
• Download the email with the patch and apply it to your local kernel repository in a test branch.
• Compile a test version of the kernel and boot from a test machine (not your production computer).
• Check Thunderbolt/USB4 peripherals: external drives, hubs, and displays, and record results to report or dismiss errors.

Note: the source text indicates the patch is on the mailing list and that the usual review process is still pending; there is no indication it has yet been integrated into a stable kernel release.

What experience do I need to do this?

You should feel comfortable compiling the kernel and booting test machines; if not, wait for official releases or seek help from specialized communities.

Review, risks, and what to watch for

What risks are involved in testing the patch right now?

Short answer: the main risk is instability and incompatibilities with other parts of the USB subsystem; that is why testing in isolated environments is necessary.

The kernel review process will verify security and compatibility; until maintainers approve the code, it may cause regressions affecting devices or power managed by the port.

How to follow the status and contribute?

You can follow the conversation on the kernel mailing list and the Asahi Linux project channels. If you find bugs, document them and share logs to facilitate review.

Verification: checklist to know if it affects you

• You use a Mac with M1, M2, or M3 and run Linux (Asahi Linux or another distribution you have adapted).
• You currently do not recognize disks or displays connected via USB-C/Thunderbolt.
• You have followed announcements on the kernel mailing list or at Asahi and have seen Sven Peter’s message.

For maintenance: keep backups, use test machines to test experimental kernels, and activate boot recovery mechanisms. Watch system logs when testing peripherals and report errors with captures and detailed description.

If you are not comfortable with compilations or your equipment is critical for work, wait for official integration into the kernel or seek help from a specialized professional.

The reality is that the work of reconstructing the electronics and the controller may open a new era for Linux users on Macs with Apple Silicon. This first step—a patch published on the kernel mailing list by Sven Peter and the Asahi Linux project—is relevant because it addresses an old deficiency: joint management of Thunderbolt and USB4. If all goes well, kernel integration will enable drives, hubs, and displays to work with the same stability as on macOS.