The new project leadership team made the decision to prioritize getting their existing work upstreamed into the Linux kernel, before working on supporting newer SOCs.
It's been going well.
The new project leadership team made the decision to prioritize getting their existing work upstreamed into the Linux kernel, before working on supporting newer SOCs.
It's been going well.
> We are pleased to announce that our graphics driver userspace API (uAPI) has been merged into the Linux kernel. This major milestone allows us to finally enable OpenGL, OpenCL and Vulkan support for Apple Silicon in upstream Mesa. This is the only time a graphics driver’s uAPI has been merged into the kernel independent of the driver itself, which was kindly allowed by the kernel graphics subsystem (DRM) maintainers to facilitate upstream Mesa enablement while the required Rust abstractions make their way upstream. We are grateful for this one-off exception, made possible with close collaboration with the kernel community.
https://asahilinux.org/2025/05/progress-report-6-15/
Alyssa didn't abandon the project, she completed it.
Are you under the impression that Linux is about to abandon OpenGL and Vulkan in favor of a new graphics API that only Alyssa could possibly implement?
Marcan already provided the tools needed to capture the data being passed back and forth between MacOS and the GPU, so you can see exactly what the newer versions of the SOC are doing that is different.
> We are pleased to announce that our graphics driver userspace API (uAPI) has been merged into the Linux kernel. This major milestone allows us to finally enable OpenGL, OpenCL and Vulkan support for Apple Silicon in upstream Mesa.
Guidance was provided...
> Maintainers who want to be involved in the Rust side can be involved in it, and by being involved with it, they will have some say in what the Rust bindings look like. They basically become the maintainers of the Rust interfaces too.
But maintainers who are taking the "I don't want to deal with Rust" option also then basically will obviously not have to bother with the Rust bindings - but as a result they also won't have any say on what goes on on the Rust side.
So when you change the C interfaces, the Rust people will have to deal with the fallout, and will have to fix the Rust bindings. That's kind of the promise here: there's that "wall of protection" around C developers that don't want to deal with Rust issues in the promise that they don't have to deal with Rust.
But that "wall of protection" basically goes both ways. If you don't want to deal with the Rust code, you get no say on the Rust code.
Put another way: the "nobody is forced to deal with Rust" does not imply "everybody is allowed to veto any Rust code".
https://lore.kernel.org/lkml/CAHk-=wgLbz1Bm8QhmJ4dJGSmTuV5w_...
To get anything done in the Linux mailing list you need iron will.
> With Linux 6.16 now out in the wild, it’s time for yet another progress report! As we mentioned last time, the Asahi and Honeykrisp Mesa drivers have finally found their way upstream. This has resulted in a flurry of GPU-related work, so let’s start there.
Seems that they are doing pretty well upstreaming their work.