this post was submitted on 08 Feb 2025
380 points (98.2% liked)

Open Source

33279 readers
298 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] uis@lemm.ee 12 points 2 weeks ago (1 children)

https://lore.kernel.org/lkml/293df3d54bad446e8fd527f204c6dc301354e340.camel@mailbox.org/

General idea seems to be "keep your glue outside of core subsystems", not "do not create cross-language glue, I will do everything in my power to oppose this".

[–] FooBarrington@lemmy.world 5 points 2 weeks ago (1 children)

This creates a lot of extra work for no benefit, as every driver that needs DMA would have to include their own copy of the DMA stuff.

[–] uis@lemm.ee 1 points 2 weeks ago (1 children)

They still can share code. Just not maintained by dma.

[–] FooBarrington@lemmy.world 3 points 2 weeks ago (1 children)

Nobody asked for the code to be maintained by DMA. The maintainer blocked a PR outside his subsystem, and even if it was part of his subsystem, the R4L approach is that C developers can break Rust code however they want.

Literally nobody suggested that the DMA maintainers should maintain Rust code.

[–] uis@lemm.ee 1 points 2 weeks ago