News for hackers. Stuff that matters.
Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by cwillu on Thursday February 12, 2026 @07:28PM (#46997294)
Nothing 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”.
Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by ceteia on Thursday February 12, 2026 @07:43PM (#46997425)
But, 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.

Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by wtallis on Thursday February 12, 2026 @10:01PM (#46998441)
Whether that's true or false depends on what your hypothetical developer wants to do in the future. When an all-new driver is written in Rust, then working on that driver will require knowing Rust. But nobody's talking about trying to re-write all the existing drivers in Rust, so there will still be plenty of C code to work on even in the DRM subsystem.
Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by ceteia on Friday February 13, 2026 @01:59AM (#46999742)
> When an all-new driver is written in Rust, then working on that driver will require knowing Rust.

But that is not what the claim is about, it is about any new driver, not a specific one.

Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by ladyanita22 on Friday February 13, 2026 @01:53AM (#46999712)
I think this is true. But that'd be nonetheless up to the subsystem maintainers.
Re:The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware by ceteia on Friday February 13, 2026 @02:06AM (#46999790)
That means that, even if a C developer used or added C bindings to DRM when wanting to write a new driver, they would be forced to write their new driver in Rust regardless. That seems to run counter to the promises made by Linus.