[PATCH] drm: add drm device name

Koenig, Christian Christian.Koenig at amd.com
Tue Sep 17 08:23:17 UTC 2019


Am 17.09.19 um 10:17 schrieb Daniel Vetter:
> On Tue, Sep 17, 2019 at 10:12 AM Christian König
> <ckoenig.leichtzumerken at gmail.com> wrote:
>> Am 17.09.19 um 07:47 schrieb Jani Nikula:
>>> On Mon, 16 Sep 2019, Marek Olšák <maraeo at gmail.com> wrote:
>>>> The purpose is to get rid of all PCI ID tables for all drivers in
>>>> userspace. (or at least stop updating them)
>>>>
>>>> Mesa common code and modesetting will use this.
>>> I'd think this would warrant a high level description of what you want
>>> to achieve in the commit message.
>> And maybe explicitly call it uapi_name or even uapi_driver_name.
> If it's uapi_name, then why do we need a new one for every generation?
> Userspace drivers tend to span a lot more than just 1 generation. And
> if you want to have per-generation data from the kernel to userspace,
> then imo that's much better suited in some amdgpu ioctl, instead of
> trying to encode that into the driver name.

Well we already have an IOCTL for that, but I thought the intention here 
was to get rid of the PCI-ID tables in userspace to figure out which 
driver to load.

I mean it could be perfectly valid to not only match the kernel, but 
also the hardware generation for that.

Christian.

> -Daniel



More information about the dri-devel mailing list