[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0db981a4-9519-ca7d-b6ce-ff498070bf8e@amd.com>
Date: Mon, 11 Jul 2022 11:50:34 +0200
From: Christian König <christian.koenig@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alex Deucher <alexander.deucher@....com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.15 138/230] drm/amdgpu: bind to any 0x1002 PCI diplay
class device
Am 11.07.22 um 11:37 schrieb Greg Kroah-Hartman:
> On Mon, Jul 11, 2022 at 11:29:53AM +0200, Christian König wrote:
>> Hi Greg & Alex
>>
>> why is that patch picked up for stable? Or are we backporting IP based
>> discovery?
> New device ids are usually added to stable trees as they are "trivial".
Ah! Ok, sounds like a misunderstanding.
For the background this is *not* a new device id, but rather changes the
way the existing device ids are discovered.
Instead of a table with device ids and hard coded list of hw blocks
inside a device, we now look at a VBIOS table to determine which hw
version/blocks are present.
So yes, this might enable new hardware but it's most likely not trivial
enough to be backported.
>> If yes, is that wise? IIRC we had quite a number of typos etc.. in the
>> initial patches.
> If this commit is incorrect, we will be glad to drop it, or add any
> needed add-on commits. Which do you want to see happen here?
Alex, that is mostly a question for you.
Thanks,
Christian.
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists