edinbruh

Well, opinions can be wrong. When someone says an opinion is wrong they don't mean that it's not true that you have that opinion, but rather that it's an opinion you should not have.

And some opinions like any other ideas are just wrong. You are entitled to have them, just as much as you are entitled to be wrong, it doesn't change the fact that it's wrong.

For example "we should change math so that 25+75=100" is an example of a wrong opinion.

If you read the documentation you would know that:

• Drivers have a part in the kernel and some others outside the kernel
• The part inside the kernel is called amdgpu most likely already installed and you don't need to do anything
• For the parts outside you can use either amd's (the ones you tried to install) or the community made ones (mesa)
• Amd's own stuff is better only in raytracing and worse in everything else, so unless you are doing raytracing you should avoid it and use mesa
• Mesa is likely already installed and you could have just done nothing, if not look up how to install that
• If you still want amd's own stuff, or if you want rocm, you should look that up on mint documentation and forum

Footnote: it is possible to install both mesa and amd's software, and set up some games to use one and some and everything else to use the other, this allows you to always use mesa, except for those games with raytracing, but seeing that you are already overwhelmed I would avoid that for now, and maybe try if when you are more experienced.

You should not ask chatgpt for these things, you should look for documentation and forums. A good place to understand how things work is the arch wiki, even if you don't use arch, most of the stuff is valid for other distros... except instructions on installing packages, that you should look in your distro's specific documentation and forums.

What is non-plain-tezxt code?

For esolang nerds. They enjoy the existence of the language, not its usage

I think Hellwig understands everything very well, he just wants things done his way, for whatever (possibly valid) reason he might have.

Literaly from your quotation: "I assume that we’re good with maintaining the DMA Rust abstractions separately [...] No, I'm not" He understands the abstractions would not be in his domain and maintained by someone else, he does not want abstraction at all.

Maybe you are not familiar with the proposal but these "separate rust abstractions" would be a separate module that depends on DMA mapping as a client and deals with cross-language issues, rust drivers would then be clients of this module, it would not be part of the DMA mapping module, it would not be mixed with the DMA code. But Hellwig doesn't want an abstraction module at all, Instead he want's you to "do that [the abstraction] in your driver so that you have to do it [maintain a cross-language codebase]".

Please notice that the abstraction module would not add any more burden on him than the drivers themselves would, because as of now C code is allowed to break Rust code. It would only remove burden from maintainers of Rust drivers, and even if it weren't it would be easier to fix just the abstraction instead of every driver.

He also refuses to have other people maintain the abstraction, this too for whatever reason, which accredits his request to not add abstraction he would have to maintain. If the abstraction were part of the core dma mapping code, I think it would be a reasonable request, but it wouldn't be.

Now, we do not know the reason why he opposes it so much. From his words it looks like he doesn't want Linux to be a cross-language codebase, which would be a valid reason in itself, but dealing with abstractions in drivers instead of a module doesn't make it any less cross-language, unless the drivers are out of tree, which they wouldn't be. Some people (e.g. Hector Martin) think that he's hoping the Rust for Linux project to fail altogether, and fore rust code to be removed from the kernel, and this obstruction would partake in that. I do not think it is that drastic, I think he just fears that those abstraction would eventually become part of what he has to maintain, and no amount of reassurance or new maintainers would change his mind.

I also don't think Martin's brigading is anything productive, and I hope that doesn't become the reason that rust code gets obstructed from being merged into the kernel, but it sure does focus the attention on these matters.

What they are asking is not to change the c code to suit rust, but to leave the C code as is, and have a single Rust-written wrapper that links into the C DMA code so that other Rust drivers can link into the wrapper. Additionally, said wrapper is not to be maintained by Hellwig, but by the maintainers of the drivers that will use the wrapper, so without overhead for Hellwig.

He is not asking to not make his work harder, he's explicitly asking to make it harder to write rust drivers that use DMA.

Ham is made from the thighs of the pig

I think it's origin is actually the same as Shrek and Fiona. In the book "Shrek!" there is a donkey that accompanies Shrek to a castle where he meets a princess uglier than him.

Source: Wikipedia

This meme is so old it uses jQuery

What is this referring to?