SRs for the following were all accepted:
- libva
- libva-gl (needs link created)
- Mesa-libva
Confirmed patches remove the need to change flags in chromium to
utilize the VA-API support.
Confirmed upstream approach for hardlinking driver instances to
gallium_drv_video.so in #dri-devel and sent patch and SR.
- http://lists.freedesktop.org/archives/mesa-dev/2015-December/103585.html
- https://build.opensuse.org/request/show/349699
Cleaned up chromium patch and placed behind %bcond. Synced pbms
package for testing (issues building on pmbs due pre-existing issue of
missing _constraints file, I sent email to packman list).
- https://build.opensuse.org/request/show/349702
Should probably add a wiki comment/page about using h264ify extension
to gain the most from this patch. Not sure if it should/can be enabled
in package.
Otherwise, everything should work out of the box for folks using r600
or radeonsi once everything hits tumbleweed.
--
Jimmy
On Fri, Dec 18, 2015 at 2:58 PM, Jimmy Berry
On Fri, Dec 18, 2015 at 10:17 AM, Sergey Kondakov
wrote: On 17.12.2015 20:24, Jimmy Berry wrote:
There had been a prior attempt to enable VA-API support in Mesa (back in Feb 2015), ...
I decided to follow the format of libvdpau-va and libvdpau-va-gl packages. Their source seems to be broken up so it was probably natural to break the package up like that. For libva I split off a linked package called libva-gl.
- libva: builds everything except gl related - libva-gl: builds libva-egl1 and libva-glx1
... For those interested in following along (SR requests pending).
libva - https://build.opensuse.org/request/show/349285 - https://build.opensuse.org/request/show/349402
libva-gl (new) - https://build.opensuse.org/request/show/349403
Mesa - https://build.opensuse.org/request/show/349404
I will followup with the chromium SR assuming these make it in.
With luck all this will be accepted/worked out over the next few days.
Enjoy!
-- Jimmy
Great work ! But shouldn't libva-gl package be a branch of libva with shared source and 2 spec-files as it's usually done on OBS ? That way they are easier to maintain and are automatically simultaneously branched into other repoes.
Yes, as I had already commented on the SR it should be a link. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org