Add VVC decode LibVA interface. #1
Open
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
ChunjuanLiu
force-pushed
the
VvcLibVA
branch
3 times, most recently
from
5d71598 to
477834b
Compare
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v3...v4) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
ChunjuanLiu
force-pushed
the
VvcLibVA
branch
4 times, most recently
from
208f416 to
732697e
Compare
XinfengZhang
force-pushed
the
VvcLibVA
branch
from
732697e to
0507018
Compare
The adapter_luid is already stored in pDriverContext->native_dpy. The copy in VADisplayContextWin32, is not needed. Signed-off-by: Emil Velikov <[email protected]>
All the vafool codebase was removed a while ago, with little sign of it coming back. Signed-off-by: Emil Velikov <[email protected]>
Note that the old ones are deprecated. For the new one mention the ownership model and num_drivers meaning/handling. Signed-off-by: Emil Velikov <[email protected]>
Similar to ce9898c Signed-off-by: Emil Velikov <[email protected]>
As documented (and updated) the callee(s) cannot set the num_drivers past the original size. So drop the unreachable code. Signed-off-by: Emil Velikov <[email protected]>
All the backends implement the callback. So this temporary check can go now. Signed-off-by: Emil Velikov <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
Fixes: 484f128 ("win32: remove duplicate adapter_luid entry") Signed-off-by: Sil Vilerino <[email protected]>
Add a debug build type run to catch errors only happening on debug
Currently there is no way of exposing the driver tile_rows and tile_cols limitations for encoding with tiles. For codecs like AV1 there is a cap specifying the max number of tiles, but without differentiating cols/rows. Different hardware may have restrictions which may need to be taken into account. More specifically, D3D12 encode exposes the maximum rows/cols and adding VAConfigAttribEncMaxTileRows/Cols allows for mapping that information to the VAOn12 driver. Signed-off-by: Sil Vilerino <[email protected]>
add new vaMapBuffer2 backend driver need some usage hint to optimize the operation Signed-off-by: Carl Zhang <[email protected]>
This new added api should be exported otherwise it will cause link issues. Signed-off-by: Tong Wu <[email protected]>
xe KMD: https://gitlab.freedesktop.org/drm/xe/kernel.git Signed-off-by: Carl Zhang <[email protected]>
As noted in the action v1 release note, action was rewritten to use qemu and libvirt which requires switch from macos to ubuntu runners. Signed-off-by: Dmitry Rogozhkin <[email protected]>
Add PRIME3 memory type defination to support create surface with extra flags.
Add symbol for exporting existing VA vaGetLibFunc function to .def file Fixes intel#782 Signed-off-by: Sil Vilerino <[email protected]>
Bumps [actions/deploy-pages](https://github.com/actions/deploy-pages) from 2 to 3. - [Release notes](https://github.com/actions/deploy-pages/releases) - [Commits](actions/deploy-pages@v2...v3) --- updated-dependencies: - dependency-name: actions/deploy-pages dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/deploy-pages](https://github.com/actions/deploy-pages) from 3 to 4. - [Release notes](https://github.com/actions/deploy-pages/releases) - [Commits](actions/deploy-pages@v3...v4) --- updated-dependencies: - dependency-name: actions/deploy-pages dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/upload-pages-artifact](https://github.com/actions/upload-pages-artifact) from 2 to 3. - [Release notes](https://github.com/actions/upload-pages-artifact/releases) - [Commits](actions/upload-pages-artifact@v2...v3) --- updated-dependencies: - dependency-name: actions/upload-pages-artifact dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
when all backend failed vaGetDisplayWl will just return a context that was already destroyed. This leads to crashes if downstream tries to use the context.
The "which" utility is not guaranteed to be installed either, and if it is, its behavior is not portable either. This means that when autoreconf is installed, the `which` check will report a fatal error because the which tool did not exist and the shell returned a nonzero status when attempting to fork+exec. If it did exist, it might not be an implementation of `which` that returns nonzero when commands do not exist. The general scripting suggestion is to use the "command -v" shell builtin; this is required to exist in all POSIX 2008 compliant shells, and is thus guaranteed to work everywhere. For some in-depth discussions on the topic, see: - https://mywiki.wooledge.org/BashFAQ/081 - https://unix.stackexchange.com/questions/85249/why-not-use-which-what-to-use-then/85250#85250 Examples of open-source shells likely to be installed as /bin/sh on Linux, which implement the 15-year-old standard: ash, bash, busybox, dash, ksh, mksh and zsh. Signed-off-by: Eli Schwartz <[email protected]>
Run autogen.sh as a dist script while creating the tarball. Also update autogen.sh to detect when it is being run from `meson dist`, and use that as the srcdir. Signed-off-by: Eli Schwartz <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
Apps like gstreamer will crash on WSL without this check, which existed before but was removed in commit f097811 Signed-off-by: Sil Vilerino <[email protected]>
Due to different HW implementation, the surface could require a different alignment size rather than the default ones, here introduces a new VASurfaceAttribute, alignment size, which contains two variables log2_width_alignment and log2_height_alignment, each has 4 bits, and the alignment needs to be left shifted 2**size from the application side. The alignment is in the powers of 2 and range in [2**0, ... 2**15] = [1, 2, 4, 8, ... 32768] And this alignment should be met when creating context as an add-on requirement. If not implemented, the existing/default alignment logic will be used. Signed-off-by: Ruijing Dong <[email protected]>
0x80000000 usually used as unsupport bit, update to new value. Signed-off-by: Li, Xin6 <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
Signed-off-by: Hirokazu Honda <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
Signed-off-by: Carl Zhang <[email protected]>
wl_drm is a legacy protocol, and wlroots is getting rid of it [1]. Use the newer and standard linux-dmabuf protocol if available to get the DRM device. [1]: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4397 Signed-off-by: Simon Ser <[email protected]>
ChunjuanLiu
force-pushed
the
VvcLibVA
branch
2 times, most recently
from
c29d7bf to
28c04ae
Compare
Signed-off-by: Xu, Zhengguo <[email protected]>
When building libva with lld (the llvm-project linker), version 17 or
later, an error similar to the following is emitted when linking
libva.so:
ld: error: va/libva.so.2.2000.0.p/va_compat.c.o: symbol
vaCreateSurfaces@VA_API_0.32.0 has undefined version VA_API_0.32.0
The root cause is that lld 17 checks linker version scripts more
strictly by default, and emits an error when undefined symbols or
undefined versions are referenced.
Earlier in the build, it turns out that due to these lld errors, va's
meson.build fails to detect `--version-script` support:
Checking if "-Wl,--version-script" : links: NO
This is because the small test program used by meson to check whether a
shared library can be linked with the `libva.syms` version script is
completely empty, and therefore the two symbols in the version script,
`vaCreateSurfaces_0_32_0` and `vaCreateSurfaces`, are undefined.
Fix the problem by providing placeholder definitions for these symbols
in the `code` argument to meson's `cc.links()` function. This ensures
that meson correctly detects `--version-script` support with lld version
17 or later, and makes it possible to link the libva shared library.
Signed-off-by: Dimitry Andric <[email protected]>
Signed-off-by: Liu, Chunjuan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.