I've added support in ffmpeg-9999; so it'll be in next snapshot and we'll have to drop your keywords if it's not keyworded remi promised to add intel support you can play with media-video/hwdecode-demos for testing it; vaapi_* programs test libva and you should see a cat on a tree; ffmpeg_* programs segfault here, not sure whose fault it is.
I've tried it on an HPPA system using X11 forwarding to an x86 with an older Nvidia graphics card which doesn't support all this modern video acceleration. I found that the ffmpeg_* test programs _did_ show the cat up the tree and the vaapi_* test programs did _not_ (because no hardware support was found on the remote display). I surmise that the ffmpeg_* programs support software fallback whereas the vaapi_* ones do not. Generally, though, I wonder whether HPPA should support this at all. Am I right in concluding that the alternative to keywording would be use.masking the `vaapi' keyword?
(In reply to comment #1) > Am I right in concluding that the alternative to > keywording would be use.masking the `vaapi' keyword? yes; at least you should be right as I'm trying to get all this under the vaapi useflag for consistency
keyworded ~arch for x86
Masked on alpha/arm/ia64/sparc
Masked USE=vaapi for HPPA.
As of right now, vaapi is pretty useless unless you've got the hardware listed here: http://www.freedesktop.org/wiki/Software/vaapi Since this depends on proprietary drivers or Intel hardware, I'm going to keep the mask for PowerPC at this time. If this changes (Open Source Nvidia/ATI support) we'll revisit this bug.
Forgot to remove us from CC, sorry.
Created attachment 261558 [details] libva-1.0.8 release ebuild Ebuild for the 1.0.8 version
Cannot keyword on FreeBSD until we add linux-compat header file package.
