[VDPAU] [PATCH] try DRI2DriverDRI name on DRI2DriverVDPAU absence
Eric Anholt
eric at anholt.net
Wed Jan 8 21:33:16 PST 2014
Aaron Plattner <aplattner at nvidia.com> writes:
> Thanks for the link, Rinat.
>
> It looks like from the discussion, that Eric (CC'd) is suggesting that
> libvdpau should enumerate and load all available VDPAU drivers and let
> each one determine, through vendor-specific mechanisms, whether it is
> applicable for the requested X screen. Eric, does that sound like what
> you're suggesting? That would be doable, but was not the approach that
> was suggested when I asked the X.Org community how the X screen-to-VDPAU
> driver mapping should be achieved when this was first being designed.
>
> Can you point me to where Mesa's DRI3 support determines which driver to
> use for which X screen?
dri3_common.c. We should really rig up a mechanism based on either
inspecting driver binaries to see what hw they support, or having a file
along the side saying what hw the drivers support, so that you don't
need all the pci ids in the build of the loader. We just haven't gotten
around to it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/vdpau/attachments/20140109/0c000c54/attachment.pgp>
More information about the VDPAU
mailing list