How about an option DRM_RADEON_FORCE_CIK that enables Radeon CIK support
even if DRM_AMDGPU_CIK is enabled? That way the default depends only on
the AMDGPU configuration and makes sense for end users and
distributions. The DRM_RADEON_FORCE_CIK option would be an override for
developers to make
Kconfig still calls CIK and SI support in amdgpu "experimental". Is that
still true? Should we stop calling it experimental if we actually want
distributions to start using it?
Regards,
Felix
On 17-04-07 03:17 PM, Alex Deucher wrote:
> On Fri, Apr 7, 2017 at 2:00 PM, Felix Kuehling
On Fri, Apr 7, 2017 at 3:47 PM, Felix Kuehling wrote:
> Kconfig still calls CIK and SI support in amdgpu "experimental". Is that
> still true? Should we stop calling it experimental if we actually want
> distributions to start using it?
I guess they aren't really
On Fri, Apr 7, 2017 at 2:00 PM, Felix Kuehling wrote:
>
> On 17-04-07 12:10 PM, Christian König wrote:
>> Am 07.04.2017 um 18:01 schrieb Felix Kuehling:
>>> Advertise CIK PCI IDs only when they are not supported by amdgpu.
>>> Use the CONFIG_DRM_AMDGPU_CIK to check so that
On 17-04-07 12:10 PM, Christian König wrote:
> Am 07.04.2017 um 18:01 schrieb Felix Kuehling:
>> Advertise CIK PCI IDs only when they are not supported by amdgpu.
>> Use the CONFIG_DRM_AMDGPU_CIK to check so that a single option in
>> the kernel config keeps both drivers in sync.
>>
>> This is
On 07/04/17 12:01 PM, Felix Kuehling wrote:
Advertise CIK PCI IDs only when they are not supported by amdgpu.
Use the CONFIG_DRM_AMDGPU_CIK to check so that a single option in
the kernel config keeps both drivers in sync.
This is the simplest possible change. A more complete solution
may want
Am 07.04.2017 um 18:01 schrieb Felix Kuehling:
Advertise CIK PCI IDs only when they are not supported by amdgpu.
Use the CONFIG_DRM_AMDGPU_CIK to check so that a single option in
the kernel config keeps both drivers in sync.
This is the simplest possible change. A more complete solution
may