Re: [PATCH] Add second DRI driver name (DRI2DriverVDPAU)

From: Eric Anholt <eric@anholt.net>
To: Rinat Ibragimov <ibragimovrinat@mail.ru>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Add second DRI driver name (DRI2DriverVDPAU)
Date: Mon, 26 Aug 2013 16:22:49 -0700	[thread overview]
Message-ID: <87haecdol2.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1377552151.192170899@f62.i.mail.ru>

[-- Attachment #1.1: Type: text/plain, Size: 1938 bytes --]

Rinat Ibragimov <ibragimovrinat@mail.ru> writes:

> Понедельник, 26 августа 2013, 13:40 -07:00 от Eric Anholt <eric@anholt.net>:
>> Ибрагимов Ринат <ibragimovrinat@mail.ru> writes:
>> 
>> > libvdpau uses second DRI driver name to determine which VDPAU driver
>> > to use. This patch will allow libvdpau choose libvdpau_i965.so on systems
>> > with Intel GPUs, libvdpau_nvidia.so on those with nVidia ones, and so on.
>> > I'm experimenting now with generic vdpau driver using OpenGL/VA-API,
>> > it would be convenient to have this driver selection working without manual
>> > driver selection.
>> 
>> If it's a generic driver, why would it need a "i965" string passed over
>> the DRI2 protocol to find it?
>
> It doesn't actually. It's just to simplify distribution package management.
> If one names driver libvdpau_nvidia.so.1, it will break VDPAU on
> nVidia equipped machines. With this patch one can name it
> libvdpau_i965.so.1 and driver will be loaded on intel equipped
> machines only.
>
>> 
>> One of the things I'm planning on doing is removing use of the
>> protocol-provided DRI2 driver name from Mesa -- Mesa knows what drivers
>> it has built, and it knows how to detect those devices (in the EGL
>> code), so why would we pay attention to what the X Server thinks our
>> driver's name is?  Seems like vdpau could probably do the same.
>> 
>
> VDPAU uses entry point library (libvdpau) which loads backend drivers.
> libvdpau uses second DRI2 driver name amongst other methods to determine
> which driver to load. It can not rely on Mesa's internal knowledge, because
> it must work with proprietary nVidia driver too.

Right, I meant "couldn't libvdpau have a method to determine which
driver to load based on looking at your hardware, like how Mesa's EGL
does?", since only libvdpau is likely to know how pieces of hardware map
to driver binaries.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx