#
✕ nick:Zollerboy1
#asahi-dev · 2024-09-30 23:11
Zollerboy1I just chose the asahi kernel as the baseline for my rust explorations, because it's still quite close to the t2-linux kernel that I need for my Intel mac and because it has a few more Rust bindings than the rust4linux kernel.
#asahi-dev · 2024-09-30 23:09
Zollerboy1chadmed_: I would love to contribute to asahi specifically, but I don't think that I can really be that useful, because I don't actually own an M1 mac ;)
#asahi-dev · 2024-09-30 22:46
Zollerboy1jannau: thanks for the link. I'm still learning to navigate the jungle that is linux kernel patches :)
#asahi-dev · 2024-09-30 22:33
Zollerboy1jannau: Yeah, I was just writing an abstraction for character device drivers in Rust (which afaics doesn't exist anywhere – but please prove me wrong^^) and was wondering if and how this could *eventually* get upstreamed. I have never submitted a patch to the linux kernel before, so I'm not quite sure on the process and also thought that in the current situation starting with a Rust patch specifically could be not such a
#asahi-dev · 2024-09-30 17:36
Zollerboy1opticron: huh? that's strange. the rest of the message was "main kernel? Thanks!" :)
#asahi-dev · 2024-09-30 15:54
Zollerboy1Also, is there anyone who I could contact if I have specific questions about the Rust APIs?
#asahi-dev · 2024-09-30 15:52
Zollerboy1Hey everyone! During my journey to learn how to write kernel modules in Rust, I noticed that the Asahi fork has quite a bit more Rust APIs than what's in the main kernel rn. Is all that extra Rust API supposed to be merged into the main kernel eventually and just held back due to the current Rust for Linux issues? Suppose I wanted to contribute to the Rust wrappers, would it be better to contribute to the Asahi fork or the