[Drdrdrq]

I don't think there is much difference between blob and such code from the kernel maintainers' point of view. From users' point of view the difference is huge (freedom to tinker / fix bugs), but maintainers need to keep the whole kernel maintainable. Merging such code would be irresponsible.

And no, I don't want just "good" code in kernel I am using. This is not business. Make it maintainable so it can get better (perfect) in the long run. (yes, I know there are places in kernel where code is not even good, let alone perfect, but that's another issue altogether)

[kuschku]

The kernel maintainers can choose between continuing with reverse engineering and hacking together their own driver, or starting with the code of AMDs driver and adapting that.

And you really think continuing with the hacky reverse engineering is the better solution?

[angelsl]

Since when did writing a driver become the kernel maintainers' problem?

I don't think the AMDGPU driver not being mainlined really affects Linux. On the other hand, AMD will really benefit from it.

[kuschku]

> Since when did writing a driver become the kernel maintainers' problem?

Since the kernel maintainers, and other open source contributors wrote drivers?

> I don't think the AMDGPU driver not being mainlined really affects Linux. On the other hand, AMD will really benefit from it.

You remember the days when Linux never would work on any real PC because audio drivers, GPU drivers, everything was missing? Do you want those back?

Having shitty drivers in the kernel isn’t ideal either, just like microkernels vs. monolithic kernels are a tradeoff, but at least cooperating with them in how to get it best into the kernel (AMD rewrote ~100k LOC since the last "Nope" from the maintainers) would be a lot more helpful than this.