| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
ld: error: unable to find library -ldl
|
|
|
|
| |
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
|
|
|
| |
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
|
|
|
|
|
| |
Bump VA-API version to 1.8.0 pre1 and libva to 2.8.0 pre1
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
|
|
|
|
|
| |
Bump VA-API version to 1.7.0 pre1 and libva to 2.7.0 pre1
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
|
|
|
|
|
|
|
|
| |
'==' is invalid posix shell syntax. With dash as /bin/sh
the check fails with:
./configure: 17656: test: yes: unexpected operator
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
|
|
|
|
|
| |
Bump VA-API version to 1.6.0 pre1 and libva to 2.6.0 pre1
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
|
|
|
|
|
| |
This reverts commit ec9536c2b1c12e43ff047ecb2ec52dea6f5b90ba to 8c80b758b133a4d88fb5d6859841bcd316a016bc
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
|
| |
|
| |
|
|
|
|
|
|
| |
Bump VA-API version to 1.5.0 pre1 and libva to 2.5.0 pre1
Signed-off-by: intel <carl.zhang@intel.com>
|
|
|
|
|
|
| |
Bump VA-API version to 1.4.0 pre1 and libva to 2.4.0 pre1
Signed-off-by: XinfengZhang <carl.zhang@intel.com>
|
|
|
|
|
|
| |
Bump VA-API version to 1.3.0 pre1 and libva to 2.3.0
Signed-off-by: XinfengZhang <carl.zhang@intel.com>
|
|
|
|
|
|
|
|
| |
Not all toolchains provide support for -fstack-protector. This patch
provides a configure check to avoid build errors like
/home/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/x86_64-buildroot-linux-uclibc/6.4.0/../../../../x86_64-buildroot-linux-uclibc/bin/ld: cannot find -lssp_nonshared
/home/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/x86_64-buildroot-linux-uclibc/6.4.0/../../../../x86_64-buildroot-linux-uclibc/bin/ld: cannot find -lssp
|
|
|
|
| |
Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
|
|
|
|
|
|
| |
Update NEWS and Bump VA API version to 1.2.0
Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
|
|
|
| |
We moved libva from github/01org to github/intel, however some files
still have links to the old 01org URLs, this commit updates these links
to the new intel URLs. In addition, this commit added a contact email
address for security issue reporting
This fixes https://github.com/intel/libva/issues/189
Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is an error below when running 'make distclean':
Makefile:496: ../drm/.deps/va_drm_utils.Plo: No such file or directory
make[2]: *** No rule to make target '../drm/.deps/va_drm_utils.Plo'.
Stop.
The regression is caused by f17486f which added subdir-objects to
AM_INIT_AUTOMAKE.
This patch comes from
https://github.com/intel/libva/pull/172#issuecomment-362182959
Signed-off-by: Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 6ca99be5042558035a78ffa87cfcd853611591cc.
Strict compilation flags are not consistent across different
versions of GCC and cause issues for users with older GCC
versions.
Since we have little control over which compiler version
is used by user, ensuring that strict compilation works properly
across all known used compilers would be a maintenance
headache.
Instead, don't enforce strict compilation and let users choose
when to enforce it via user-defined C/CXXFLAGS.
Fixes #152
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
|
|
|
|
|
|
|
|
| |
Use -Wall -Werror compiler flags for stricter compilation.
Fixes #146
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The APIs/data structures defined in va_tpi.h and va_egl.h are used
to implement buffer sharing between libva and the 3rd party libraries.
We have an official buffer sharing machnism in VA core, so libva-tpi and
libva-egl are unnecessary any more.
However va_egl.h or va_tpi.h is included uselessly in a few places,
e.g. https://github.com/01org/libyami/blob/apache/vaapi/vaapidisplay.h#L22
So va_egl.h and va_tpi.h are kept with a deprecation warning message.
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
| |
ABI was broken in the previous versions, so we will bump the VA API version
to 1.0.0 and library version to 2.0.0 for next release. Some data
structures will be changed or removed in the next commits
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
| |
Some new definitions were added for FEI, so bump a new VA API version
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Notify user an error if user provides --enable-x11/--enable-glx/--enable-egl/--enable-wayland
however the requirement can't be met. drm has been checked mandatorily
in the script
v2: Remove XEXT_CFLAGS/XFIXES_CFLAGS from va/x11/Makefile.am and use
$X11_PKG_ERRORS in the error message if the requirement is met for VA/X11
This fixes https://github.com/01org/libva/issues/68
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
Reviewed-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
|
|
|
|
|
|
|
|
| |
Doing the runtime lookup is error-prone (as indicated in the code
already by the two library names) and not necessary at all.
Just compile wl_drm_interface as part of libva which is the usual
way to use extra Wayland protocols. Care must be taken as to not
accidentally export the symbol though.
|
|
|
|
| |
Signed-off-by: Philipp Kerling <pkerling@casix.org>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
| |
No one is interested in this dummy driver and it is not maintained.
This fixes https://github.com/01org/libva/issues/28
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I believe shipping wayland-drm-client-protocol.h is wrong: The header
should always be generated by the wayland-scanner that matches the
runtime wayland version. Currently when someone clones the repo and
builds, the shipped version is used.
Remove wayland-drm-client-protocol.h from source tree, modify the
build so the header is considered a built source file, and make
configure fail if wayland is enabled but wayland-scanner is not found.
Fixes #34.
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
|
|
|
|
|
|
|
|
| |
on by default, but allows optional disabling.
fixes #21
Signed-off-by: Sean V Kelley <seanvk@posteo.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
debian control files are maintained by packagers
Yes there is a "convenience" factor to roll your
own debian package, but this is not maintained by
us and represents a fork from debian packagers.
As with the bit rot of libva.spec, remove this.
fixes #18
Signed-off-by: Sean V Kelley <seanvk@posteo.de>
|
|\
| |
| | |
test: remove from library
|
| |
| |
| |
| |
| |
| |
| |
| | |
Moved to libva-utils
Fixes #12
Signed-off-by: Sean V Kelley <seanvk@posteo.de>
|
|/
|
|
| |
Signed-off-by: Sean V Kelley <seanvk@posteo.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead the user must call vaDestroyBuffer() to destroy a buffer explicitly.
If following the previous API specification,
1. Violate "who allocate who release" principle
2. The user cannot re-use VA buffer flexibly
3. The user still has to call vaDestroyBuffer() to destroy the buffers which
are not going to be passed to vaRenderPicture()
We discussed the change at https://bugs.freedesktop.org/show_bug.cgi?id=97970
v2: bump version to 0.40 because this is a incompatible change to VA-API
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
|
|
|
| |
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|