5 ms·
> Dave Airlie just announced in the Maintainers Summit that the DRM subsystem is only ""about a year away"" from disallowing new drivers written in C and requir
by davikr 8mo ago
> Dave Airlie just announced in the Maintainers Summit that the DRM subsystem is only ""about a year away"" from disallowing new drivers written in C and requiring the use of Rust.
wow
- jeroenhd 8mo agoWhen the C absolutist maintainers fought for control over the ability to keep Rust out of their ballpark, I didn't expect the reverse to happen. Still, I think it makes a lot of sense. Completely new GPU drivers are quite rare and the macOS drivers from Asahi are a showcase proving that Rust and GPU drivers work together well. If there's any subcomponent switching to Rust-first for new contributions, it makes sense for it to be the one that had already been proven to be Rust-compatible.
- imcritic 8mo agoAsahi project looks barely alive, almost abandoned. I know that their explanation of low activity is that they are being active elsewhere, supposedly pushing all their work upstream, but this has been happening for months and they don't give any reports about their progress, so I'm worried it will all die soon. And given that the project barely brought some Linux compatibility for m1 and m2 hardware and no prospects for bringing similar compatibility for newer generations - I fear it all will be kinda useless in the end.
- kryptiskt 8mo agoWasn't it just a couple of weeks ago that they started supporting M3? That smells like progress to me.
- mathfailure 8mo agoOne can start working on creation of a teleportation device. Doesn't mean we have it. https://asahilinux.org/docs/platform/feature-support/m3/ https://asahilinux.org/docs/platform/feature-support/m3/ What do you see as progress here? Nothing is supported, everything is "to be announced" (i.e. unsupported).
- throawayonthe 8mo agothey likely meant this progress post showing a desktop booting on an M3 mac: https://www.reddit.com/r/AsahiLinux/comments/1qnddjd/m3_now_has_fedora_43_asahi_remix_working_with_kde/ https://www.reddit.com/r/AsahiLinux/comments/1qnddjd/m3_now_... albeit with software graphics
- mathfailure 8mo agoLooks believable that they are indeed the devs behind the project, but it's weird to post stuff like that to... reddit? They have a site for the project, why not post there?
- cermicelli 8mo agoYou could read the updates... https://asahilinux.org/2025/10/progress-report-6-17/ https://asahilinux.org/2025/10/progress-report-6-17/ Not marketing a not yet complete feature on their website makes total sense. People on internet hating Asahi linux just cause seems like weird to me.
- c0balt 8mo ago> this has been happening for months and they don't give any reports about their progress This seems a bit exaggerated, their latest progress report is barely two months old: https://asahilinux.org/2025/12/progress-report-6-18/ https://asahilinux.org/2025/12/progress-report-6-18/ They inarguably have slowed down, but this should be expected as the project matures. It has also inevitably now faced the time when new generations of contributors are needed as existing ones retire/ move to other projects.
- charcircuit 8mo ago>as the project matures How can it be mature if it can't even boot on newer MacBooks. The slowness does not seem to be due to running out of impactful work that needs to be done.
- GeekyBear 8mo agoThe new leadership team blogged last year that their priority would be on upstreaming their existing work. > Our priority is kernel upstreaming. Our downstream Linux tree contains over 1000 patches required for Apple Silicon that are not yet in upstream Linux. The upstream kernel moves fast, requiring us to constantly rebase our changes on top of upstream while battling merge conflicts and regressions. Janne, Neal, and marcan have rebased our tree for years, but it is laborious with so many patches. Before adding more, we need to reduce our patch stack to remain sustainable long-term... Where do the M3 and M4 fit in? Until upstreaming and CI progress, the core team cannot prioritize new hardware. https://asahilinux.org/2025/02/passing-the-torch/ https://asahilinux.org/2025/02/passing-the-torch/ I think the majority of that upstreaming work (that isn't on hold until the kernal is ready for the Rust graphics driver to land) has happened and additional features like DP alt mode for USB C have been demoed. The next update from the team should land on their blog after 6.19 ships
- electronsoup 8mo agoThat's some weird gatekeeping. The hardware they do support is supported well.
- jeroenhd 8mo agoActivity has died down as a result of general Linux kernel developer drama, petty in-fighting, and other factors, but that doesn't change the results they did produce during their most prolific phase so far. Without proper support from upstream like AMD, Intel, and Qualcomm (to some extent) are doing, Linux will never work as well on Apple's hardware as it does on normal hardware.
- pantalaimon 8mo agoI would envision to see some more GPU drivers from Chinese companies like MooreThreads
- anthk 8mo agoThe Rust crustaceans should apply their knowledge to Redox OS and top sending Rust crapware (which it might be fine for security, but Cargo it's a nightmware to maintain) and stop messing with GNU/Linux and, by proxy, the rest of the BSD's. As tons of distros adopted LibreSSL, it might happen the same with KMS/DRM+MESA as it happened with Xenocara for X.org under OpenBSD and the special X server under NetBSD for legacy machines with really weird adapters leaving out the modular X.org -mainstream- to ports. They might call it VEGA (for MESA) and Iridium (for Gallium middleware).
- neobrain 8mo ago> Cargo it's a nightmware to maintain To my knowledge, the Linux kernel doesn't use Cargo to build Rust code.
- rjsw 8mo agoMeans that other platforms need to allow Rust in the kernel too in order to use future drivers.
- deleted 8mo ago[deleted]
- saidinesh5 8mo agoWhat do you mean other platforms? Also they can just expose c bindings to these rust libraries no?
- rjsw 8mo agoThe old drivers are mostly dual GPL or MIT licenced, they have been used in all the BSD variants.
- fowl2 8mo agoWindows already does, so you’re talking about the BSDs or Darwin?
- ladyanita22 8mo agoBSDs and other Open Source OSes that rely on Linux drivers. Windows probably has not many (or any) drivers ported from Linux.
- anthk 8mo agoPlease, stop pluralizing "BSD's", every BSD it's different and OpenBSD only reuses Linux drivers for KMS/DRM; FreeBSD has special layers and tons of drivers ported and NetBSD it's closer to philosophy in design.
- ladyanita22 8mo agoI will pluralize as all of them port some drivers from Linux
- hexo 8mo agothat is so ridiculous.
- ceteia 8mo agoWeren't the old Linux kernel developers promised the opposite by Linus Torvalds? That they would be able to continue writing in C? https://lkml.org/lkml/2025/2/20/2066 https://lkml.org/lkml/2025/2/20/2066 > The document claims no subsystem is forced to take Rust
- monocasa 8mo agoDave Airlie is saying that the subsystem maintainers are themselves choosing to move to Rust.
- ceteia 8mo agoBut what about this statement that Linus wrote: > That's been made clear pretty much from the very beginning, that nobody is forced to suddenly have to learn a new language, and that people who want to work purely on the C side can very much continue to do so. If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.
- cwillu 8mo agoNothing is happening “suddenly”, and it remains true that “people who want to work purely on the C side can very much continue to do so”.
- ceteia 8mo agoBut, is this true or false? > If any C developer developed drivers in C previously for the DRM subsystem, they might in the future be forced to learn Rust.
- ladyanita22 8mo agoI think this is true. But that'd be nonetheless up to the subsystem maintainers.