Debian Patches

Status for qcom-va-driver/1.1.0-1

Patch Description Author Forwarded Bugs Origin Last update
0001-Build-and-install-the-hardware-tests.patch Build and install the hardware tests
Upstream ships hardware tests under tests/ but no build rules for
them; each source file documents its own compiler command instead.
Add a "tests" option (disabled by default) that builds the decoder,
encoder and VPP tests and their failure-injection helpers and
installs them together with the Python test scripts under
$libexecdir/qcom-va-driver/tests, in one subdirectory per test suite
matching the source tree.

av1.py and error-recovery.py compile their helpers at runtime, which
would require a compiler on the device under test. Make them use the
prebuilt helpers installed next to them when present and fall back
to compiling them when run from a source checkout.		 Christopher Obbard <chris.obbard@oss.qualcomm.com> no 2026-10-26
0002-Install-the-driver-as-qcom_drv_video.so.patch Install the driver as qcom_drv_video.so
The project was renamed to qcom-va-driver, but the driver was still
installed as v4l2_drv_video.so. Use qcom_drv_video.so so the driver
name matches the project and LIBVA_DRIVER_NAME=qcom selects it.

The msm_drv_video.so symlink is kept and now points to the new file.
On Qualcomm MSM devices libva falls back to the DRM driver name and
without it the driver would not be picked up automatically.

The old v4l2 name is still installed as a symlink so existing
LIBVA_DRIVER_NAME=v4l2 setups keep working. It is controlled by the
new v4l2_symlink option, which defaults to true. Distributions that
never shipped the old name can turn it off with -Dv4l2_symlink=false.

Update the tests, documentation and CI to use the new name.		 Christopher Obbard <chris.obbard@oss.qualcomm.com> no 2026-10-26

All known versions for source package 'qcom-va-driver'

Links