2014-11-20, 14:24
In case of interest...
... at some point during testing different Mesa versions (10.3, 10.4rc, 10.5git) I lost vdpau hardware acceleration on my amd e350 in xbmc 13.2 and 14beta. I shuffled mesa versions and sometimes accel would be back, but some days later was absent again after small mesa updates.
At some point acceleration would not come back despite the version and even tearing was introduced (by mesa 10.5git or by enabling kdes option to disable compositing for fullscreen apps).
I found, that I had to force this in .bashrc:
one arch bug report says you also should set export LIBVA_DRIVER_NAME=vdpau also, but it works for me so far without (I am on suse). Does someone know what this variable is for? And does anyone have an idea what could have caused the switch from VDPAU_DRIVER=r600 to =va_gl?
cheers tomme.
... at some point during testing different Mesa versions (10.3, 10.4rc, 10.5git) I lost vdpau hardware acceleration on my amd e350 in xbmc 13.2 and 14beta. I shuffled mesa versions and sometimes accel would be back, but some days later was absent again after small mesa updates.
At some point acceleration would not come back despite the version and even tearing was introduced (by mesa 10.5git or by enabling kdes option to disable compositing for fullscreen apps).
I found, that I had to force this in .bashrc:
Code:
export VDPAU_DRIVER=r600
one arch bug report says you also should set export LIBVA_DRIVER_NAME=vdpau also, but it works for me so far without (I am on suse). Does someone know what this variable is for? And does anyone have an idea what could have caused the switch from VDPAU_DRIVER=r600 to =va_gl?
cheers tomme.