The Exciting Features Of The Linux 4.9 Kernel

[chithanh]

Sure, there are all sorts of ways to work around it, but it breaks an existing set up which is generally not allowed; user updates kernel, X breaks. If you are going to jump through all of these hoops, you can just as easily explicitly enable CI support in amdgpu in the kernel on your system.

Sorry, but that is bollocks.

As long as the option exists to have backwards compatibility with old userspace, it doesn't matter for that purpose whether it is enabled or disabled by default. Case in point, CONFIG_SYSFS_DEPRECATED.
Users and distributors can be expected to configure their kernels correctly according to their userspace.

And there are good reasons to have it enabled by default.

[DerCaveman]

In theory, the situation you described could be resolved by making amdgpu.ko implement the radeon.ko interface.

From the current looks of the state of amdgpu.ko and radeon.ko in 4.9rc1, it cannot be decided which option is going to happen:

• radeon.ko will be deleted from the kernel and amdgpu.ko does not implement the deleted interface, or
• radeon.ko will be deleted from the kernel and amdgpu.ko will implement the deleted interface, or
• radeon.ko will stay in the kernel for the following 10 years

Personally, I am in favor of the 1st option. That said, I am unable to predict which option is going to prevail in the forthcoming years.

What about users who need radeon.ko because their card isn't supported by amdgpu.ko?

[atomsymbol]

What about users who need radeon.ko because their card isn't supported by amdgpu.ko?

Good question.

GCN1.0+GCN1.1 support is both in amdgpu.ko and radeon.ko. Maybe the 1st step can be: remove GCN1.x support from radeon.ko.

[ownaginatious]

The problem might be resolved be compiling the "amd-staging-4.7" branch from https://cgit.freedesktop.org/~agd5f/linux/

I shortly tested it with [email protected], but on my machine+display there is no major benefit in favor of amd-staging-4.7 compared to the mainstream 4.9.0-rc1 kernel.

Yeah, I'm using a compiled version of that branch right now, but unfortunately, I'm stuck at [email protected], even though I can to 60Hz under Windows. Any ideas where I can submit issues? I had the same issue with Nvidia's proprietary drivers, and after pestering enough, they identified and fixed the issue (something to do with a weird EDID for my display). I could basically forward the details of that along and hope a similar fix can be done.

[Ansla]

amdgpu can not be made the default for SI and CIK until it reaches feature parity with radeon. As long as DAL is not merged user will be faced with a serious regresion: no more audio over HDMI / DP. Only after that you can start worying about userspace being ready for amdgpu on old distros.

Also, radeon will not be removed in the forseable future. Even if amdgpu takes over all GCN cards there is still a matter of supporting the older Radeon cards.

[atomsymbol]

amdgpu can not be made the default for SI and CIK until it reaches feature parity with radeon. As long as DAL is not merged user will be faced with a serious regresion: no more audio over HDMI / DP. Only after that you can start worying about userspace being ready for amdgpu on old distros.

Audio over HDMI works fine on my R9 390. I don't remember having any amdgpu-specific audio issues due to switching from radeon.ko to amdgpu.ko.

$ lspci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (rev 80)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio

[aironeous]

This kernel 4.9rc1 disconnected my wifi and there is no way to turn it back on but I could tether to my phone to get internet access. I removed this kernel.