Getting a high-level language driver upstreamed in Linux is of course unrealistic, so user space drivers it is.
There's work being done on source-level translation from Rust code to C (mrustc is part of this of course, but nowhere near complete), so I'm not sure why this should be seen as unrealistic.
I don't see why using mrustc to generate C code would make Rust drivers more upstream-able in the Linux kernel?
As far as I understand it, the main thing is that the team (Linus at least) does not want to maintain source code in multiple languages.
Comments
There's work being done on source-level translation from Rust code to C (mrustc is part of this of course, but nowhere near complete), so I'm not sure why this should be seen as unrealistic.
I don't see why using mrustc to generate C code would make Rust drivers more upstream-able in the Linux kernel? As far as I understand it, the main thing is that the team (Linus at least) does not want to maintain source code in multiple languages.
I do like the mrustc effort though.