C Job Security

... I added "It may even be wort writing a new, simpler and intrinsically safe scheduler in Rust", and then deleted because I thought I was probably talking out of my ass. But as it turns out:

https://vt.social/@airlied@fosstodon.org/113052975526246061:

> you and Christian are not going to solve this roadblock without and intermediary. As Danilo works his was through the roadblocks to upstream drivers, this is something we expect to engage with in terms of the bigger picture. We have an engineer looking into this, but I'm also not against a rust reimplantation if it's useful beyond asahi

To which Lina replied:

> the scheduler in the driver [...] will be roughly modeled after drm_sched (just much simpler and idiomatic Rust) and it shouldn't have any driver dependencies, so if Nova wants to use it it would be simple to pull out into common code.

So yeah, the job security angle is completely wrong. It's just a maintainer doing his job. At the same time there are people like Dave that handle the overall interaction between subsystems, are aware of what's going on, and are recruiting help towards removing the roadblocks.