commit | d52969f3a058933a8c3650825707b626d8d40e37 | [log] [tgz] |
---|---|---|
author | U. Artie Eoff <ullysses.a.eoff@intel.com> | Fri Nov 17 15:30:34 2017 -0800 |
committer | Xiang, Haihao <haihao.xiang@intel.com> | Fri Dec 01 11:29:18 2017 -0800 |
tree | f1b6f11600ff32ddab9f4aa472568bfa6abc4618 | |
parent | 071dd74acbf6ddf675924dc579771e226f87f7a9 [diff] |
test: allow user-defined driver name for test execution Some tests manipulate the LIBVA_DRIVER_NAME environment variable for various reasons. This causes tests that execute later on to behave unexpectedly. Store the original user-defined LIBVA_DRIVER_NAME before every test runs and restore it to the original value when each test finishes. This allows the test suite to be executed with any VAAPI driver. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
#Libva-utils Project
libva-utils is a collection of utilities and examples to exercise VA-API in accordance with the libva project. --enable-tests (default = no) provides a suite of unit-tests based on Google Test Framework. A driver implementation is necessary to properly operate.
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.
If you would like to contribute to libva, check our Contributing guide.
We also recommend taking a look at the ‘janitorial’ bugs in our list of open issues as these bugs can be solved without an extensive knowledge of libva-utils.
We would love to help you start contributing!
The libva-utils development team can be reached via our mailing list and on IRC in channel ##intel-media on Freenode.
We also use #Slack and host VAAPI Media Slack Team. You can signup by submitting your email address to our Slack Team invite page.
Slack complements our other means of communication. Pick the one that works best for you!