You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the RPMFusion review for libvdpau-va-gl we discussed ways to enable this by default for people who have the hardware. We'd like to move that discussion upstream.
Alternatively, maybe an /etc/profile.d hack to set VDPAU_DRIVER could be considered in the interim? Is there a decent way to detect if compatible hardware is in use other than checking if the kernel module is loaded?
Also Nicolas mentioned optimus hardware as a potential issue also. If we decided to hack the environment variable in we'd probably want to see about patching optirun to drop it as well.
Thanks for any suggestions!
The text was updated successfully, but these errors were encountered:
The only proper way I see is to patch intel driver for second DRI2 name. All other solutions are fragile. If you add VDPAU_DRIVER to environment for all users, it will break VDPAU for all non-intel users (if some of them decides to install the package).
There is another possible solution comes to mind. One can create proxy VDPAU driver (which will be loaded on any hardware by setting VDPAU_DRIVER) and implement selection logic there. :-)
optimus hardware
I don't have optimus hardware, but I heard that optirun does nothing to pass VDPAU calls. Maybe that was about primus, I'm not sure.
During the RPMFusion review for libvdpau-va-gl we discussed ways to enable this by default for people who have the hardware. We'd like to move that discussion upstream.
Doing it in the intel driver seems to have been rejected, and you seemed to think patching vdpau wouldn't fly either. Is there another way this could be done properly?
Alternatively, maybe an /etc/profile.d hack to set
VDPAU_DRIVER
could be considered in the interim? Is there a decent way to detect if compatible hardware is in use other than checking if the kernel module is loaded?Also Nicolas mentioned optimus hardware as a potential issue also. If we decided to hack the environment variable in we'd probably want to see about patching
optirun
to drop it as well.Thanks for any suggestions!
The text was updated successfully, but these errors were encountered: