Ken Moffat wrote:
On Sun, Jul 06, 2014 at 08:23:04PM -0500, Bruce Dubbs wrote:
In ticket #5232 libvdpau-0.8 is specified as a new version.  I can build it
and 'make check' runs without problem.  I'll update the package if I can
figure out how to test it.

How do I know it it's being used and if it's working properly?

Anyone know?

   -- Bruce

for "being used" -

  ISTR that I saw messages about its omission (probably on stderr)
when I started xine (ui) on an AMD box.  From past contributions, I
think it might get used on intel graphics as well as nouveau, but I
cannot confirm that.

(and therefore, "I have no idea" for the "working properly"
question.)

I got that error too.  Installed libvdpau-0.8 and re-ran xine.  Now I get:

Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
object file: No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.

I did find this in the ChangeLog for the Intel driver:

"Since 2010, DRI2 supports multiple driver names. That was added to ease
 selection of appropriate driver by libvdpau. As for today, intel driver
 support only DRI2DriverDRI (== 0), but not DRI2DriverVDPAU (== 1).

 Although there is no any hardware-specific VDPAU driver for intel video
 adapters at the moment, it would be easier to use generic drivers like
 libvdpau-va-gl by creating symlink named libvdpau_i965.so.1. That way
 appropriate driver will be selected in run time automatically:
 libvdpau_i965.so.1 on i965 equipped machines, and libvdpau_nvidia.so.1
 on nvidia equipped ones.

 [ickle: Whilst I think this is a workaround for a brainfart in libvdpau
 that it defaults to libvdpau_nvidia.so rather than first to
 libdvpau_${DRI2DriverDRI} and then to a hardcoded libvdpau_backend.so,
 I have no better solution, and this does seem in accordance with the
 spec.]"

I don't know how to interpret that.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to