it is used to fix such issue, version from libva-utils and libva is different.
because older libva-utils should also work with newer libva.
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
Since intel/libva#250, driver names are no longer restricted
to a whitelist. Thus, any driver name is legal except for
a few corner cases (i.e. empty name and name > 255 chars).
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Conformance tests should be as generic as possible and
not assume availability of any specific driver.
Fixes#93Fixes#94Fixes#95
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
The locally generated va_version.h was erroneous and
not even being used in the tests. This is because
va/va.h already includes the "real" va/va_version.h.
Thus, remove local va_version.h.in.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
The header is only needed in one compilation unit.
Thus, move it's contents to the compilation unit to
reduce unnecessary complexity and maintenance.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
880 (480 direct, 400 indirect) bytes in 1 blocks are definitely lost in loss
record 13 of 15
at 0x4C2EF35: calloc
by 0x503FF12: va_newDriverContext (in /usr/lib/libva.so.2.0.0)
by 0x4E39F63: vaGetDisplayDRM (in /usr/lib/libva-drm.so.2.0.0)
by 0x11ADD1: VAAPI::VAAPIFixture::getDisplay() (test_va_api_fixture.cpp:80)
by 0x15133E: VAAPI::VAAPIInitTerminate_vaInitialize_vaTerminate_Bad_vaSetDriverName_Test::TestBody()
Signed-off-by: Victor Toso <victortoso@redhat.com>
Some tests are specific to a particular driver (e.g. i965).
Thus, name them appropriately.
Ideally, driver specific tests should not exist in this
suite. Rather, these should be in the driver project's
test suite if it makes sense.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
If LIBVA_DRIVER_NAME is defined before this test executes,
then it will fail since the setenv overwrite parameter was
set to 0. Thus, set the overwrite parameter to 1 to force
setenv to overwrite the previous setting.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
This initial set of files covers the va.h API for all the
functions used to exercise successfully the VA-API.
Tests are divided per VA-API function with a common Fixture that
contains all calling functions to the VA-API. For the use cases
covered already there are tests for the proper functionality and also
for expected error situations.
The tests creates combinations with all the inputs to the VA-API function
and then it checks the results based on what the driver implementation reports
as supported
The set of tests can be run on any h/w supported and any driver.
The VendorString test is assuming Intel i965 driver, please help
adding the test for other drivers
More tests will be continously added
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
Sil Vilerino