Add intel-vaapi-driver 2.3.0.pre1 and update NASM, Yasm, FFmpeg, xine-lib, and VLC #970
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The project moved to GitHub, and releases are only published there. Update the source URL accordingly. The change-log is available [online][1]. [1]: https://github.com/intel/libva/blob/master/NEWS
|
The packages below need to be rebuilt. |
The project moved to GitHub, so update the source URL. [1]: https://github.com/intel/libva-utils/blob/master/NEWS
[Description][0]: > VA-API (Video Acceleration API) user mode driver for Intel GEN > Graphics family > > VA-API is an open-source library and API specification, which provides > access to graphics hardware acceleration capabilities for video > processing. It consists of a main library and driver-specific > acceleration backends for each supported hardware vendor. > > The current video driver backend provides a bridge to the GEN GPUs > through the packaging of buffers and commands to be sent to the i915 > driver for exercising both hardware and shader functionality for video > decode, encode, and processing. [1]: https://github.com/intel/intel-vaapi-driver
|
I guess it will install a libva.so.2. And to save the hassle of removing/updating the other ffmpeg deps down the road, I'll opt for a compat package. As for avidemux, and incase no compat package is made available (see pkg, the reason for the last update of libva) a working binary could be simply achieved by placing the lib in the package. |
The release is from August 2014, and the [change-log][1] is below. > Changes from 1.2.0 to 1.3.0: > > * Add AMD TBM instructions. > * Add HSW TSX instructions. > * Fix “pmulhrw”, “vphaddudq”, and “vpbroadcastq” instructions. > * Add Intel SHA, ADX, RDSEED, and SMAP instructions. > * Use a larger hash table size in NASM macro handling. > * Add support for x32 ABI (called “elfx32”). > * Add support for “function” decorator in win32/win64 object files. > * In Mach-O, only warn on repeated flags if the new flags are > different. FFmpeg failed to build with NASM, I wanted to try Yasm, but in the end it worked fine with a newer NASM. Add the update anyway. But NASM seems to be under more active development. [1]: https://yasm.tortall.net/releases/Release1.3.0.html
Rebuild against libva.
Rebuild against libav 2.0.3.
Released on November 7th, 2018.
The change-log is available [online][1].
This update fixes build errors like below in FFmpeg 3.4.5.
libavfilter/x86/avf_showcqt.asm:183: error: invalid combination of opcode and operands
libavfilter/x86/avf_showcqt.asm:183: error: invalid combination of opcode and operands
CC libavformat/adp.o
CC libavformat/ads.o
CC libavformat/adtsenc.o
CC libavformat/adxdec.o
libavfilter/x86/avf_showcqt.asm:187: error: invalid combination of opcode and operands
libavfilter/x86/avf_showcqt.asm:187: error: invalid combination of opcode and operands
[1]: https://www.nasm.us/pub/nasm/releasebuilds/2.14/doc/nasmdoc.txt
pmenzel
force-pushed
the
add-intel-vaapi-driver-2.3.0-pre1
branch
from
49c5449
to
ee8df4d
Compare
|
I updated NASM and rebuilt xine-lib and FFmpeg (only updating the patch levels, so they should be compatible). Could you test avidemux please? |
pmenzel
changed the title
|
Ignore my request, avidemux needs libva directly, and not indirectly over FFmpeg. My bad. I’d like to avoid a compatibility package, and maybe avidemux can be rebuild too? |
|
Avidemux seems to build/work with with libva-2xy, so I think libva-1xy can safely be dropped. |
|
Cool, thank you for testing. Will you update/rebuild the Avidemux? |
|
Yepp, after the dist. 'guess there are not so many avidemux users around. |
This adds the function `__vaDriverInit_1_3` to the drivers. Tested on *keineahnung* (Intel) and *inbetweenmove* (AMDGPU).
Currently, only VDPAU is supported. But we want VA-API to be supported
as well.
checking libavutil/avutil.h usability... yes
checking libavutil/avutil.h presence... yes
checking for libavutil/avutil.h... yes
checking for LIBVA... yes
checking for LIBVA_DRM... yes
checking for LIBVA_X11... yes
checking for LIBVA_WL... yes
checking libavcodec/vaapi.h usability... yes
checking libavcodec/vaapi.h presence... yes
checking for libavcodec/vaapi.h... yes
configure: VA API acceleration activated
Playing a movie, the VA-API is automatically used.
libva info: VA-API version 1.3.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_3
libva info: va_openDriver() returns 0
Increment revision to 1.
pmenzel
force-pushed
the
add-intel-vaapi-driver-2.3.0-pre1
branch
from
6e002ad
to
bbd0392
Compare
pmenzel
changed the title
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This driver is needed to get the Chromium browser working with VA-API.
libva needs to be updated too.
Install with the commands below.