Ибрагимов Ринат <ibragimovrinat@xxxxxxx> 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? 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.
Attachment:
pgpPCZ_5SCaD9.pgp
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
