3 ms·
> This also make the core feature of bootstrapping Linux on new hardware more difficult. No, Rust is currently only for drivers that aren't on that hardware an
by bronson 2y ago
> This also make the core feature of bootstrapping Linux on new hardware more difficult.
No, Rust is currently only for drivers that aren't on that hardware anyway. You can continue to build and use the kernel without Rust just fine.
For now... Maybe one day that discussion will become relevant.
- Joel_Mckay 2y agoThe drama started because of the core memory API argument. That day is today my friend =3
- steveklabnik 2y agoYou’re simply incorrect, in a way that Linus himself very clearly stated. The drama started because Rust used an API written in C. It doesn’t contain any Rust at all. Nothing has changed in this regard.
- Joel_Mckay 2y agoIt was my understanding the request was to have the core maintainer take on the additional task of supporting the rust API on top of the existing wrapper. I could be wrong, but a branch or fork seems like the easiest solution. =3
- steveklabnik 2y agoYou misunderstood.
- dralley 2y agoYour understanding is completely wrong. There was no such request, and that concern was almost immediately addressed by spelling out very directly that no such expectation existed. https://lore.kernel.org/rust-for-linux/2b9b75d1-eb8e-494a-b05f-59f75c92e6ae@marcan.st/T/#mace05a0a97522193876bb38e6f64a6ca941a59d8 https://lore.kernel.org/rust-for-linux/2b9b75d1-eb8e-494a-b0...
- oskarkk 2y agoYes, and that API is needed for drivers written in Rust. So it's not like core parts of the kernel are being now written in Rust, it's still just specific Rust drivers.