commit 011a7574957da8d5deb5dfd3e99fba7f3c4d50af
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:33:23 2026 +0000
d/README.Debian: document the Iris firmware tested on X1E80100
Older Iris firmware on X1E80100 causes intermittent decoder startup
failures, which were also hit when testing this package on that
platform and required a newer firmware. Document the firmware version
upstream tested with and how to check the installed version, so users
can rule out the firmware before investigating driver failures.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit 13dbec7c571f6b3eaf5b768b6050a2d174f378d9
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:32:19 2026 +0000
d/README.Debian: note the kernel used for upstream testing
Upstream has tested the driver on the Radxa linux-7.0.11 kernel
branch, not on mainline with only the five Iris patches applied, and
has not yet confirmed the latter is sufficient. Document this so that
users investigating failures on other kernels know that missing
kernel changes may be the cause.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit f862a21fe98130742385e594c1629a2aa38e7979
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:30:32 2026 +0000
d/scripts/qcom-va-driver-tests: add a time limit to each test
A test which hangs, for example waiting on a buffer the hardware never
returns, stopped the whole run: the remaining tests were not run and
no summary was printed.
Run each test under timeout(1) with a default limit of 10 minutes,
or an hour for the longer decoder/error-recovery and decoder/av1
runs, and count a test which is stopped as a failure. Use
--foreground so that Ctrl-C still interrupts the current test; the
Python tests already limit each command they run themselves.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit 893e345841e5dbe09e83a5a58c044a44b3004ed6
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:26:16 2026 +0000
d/scripts/qcom-va-driver-tests.1: add a manual page
Lintian warns that /usr/bin/qcom-va-driver-tests has no manual page
(no-manual-page). Add a minimal one describing what the script does,
where its output is kept and its exit status, and install it with
dh_installman.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit 8e54608b6f0a8dc1dc0d904b100a66f304981e2e
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:25:04 2026 +0000
d/scripts/qcom-va-driver-tests: skip tests whose requirements are missing
The AV1, GStreamer and Vulkan tests need hardware support or optional
dependencies which are not available everywhere: SC8280XP cannot
decode AV1, and aomenc, the GStreamer elements or a Vulkan device may
be missing. Until now these cases were reported as failures, which
made it hard to tell real regressions from unsupported setups.
Check the capabilities and dependencies before running these tests and
record a skip with the reason instead. When the requirements are met,
failures are still reported as failures. Recommend the tools used for
the checks and document the behaviour in README.Debian.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit d5e98534d3b432253b49bbd3ca8b290efdd8d178
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:16:15 2026 +0000
d/scripts/qcom-va-driver-tests: use a separate directory for each test
Several tests shared an output directory: the async tests all wrote
async.h264 to $out/async, and the H.264 and HEVC variants of the
writable-export and FFmpeg smoke tests shared their directories too.
Later tests overwrote the logs, streams and summaries of earlier ones,
so the output of a failing test could be gone by the end of the run.
Give each test its own directory named after the test, created when
the test is run, instead of a hand-maintained list of shared ones.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
commit 109967de2f7f707d56916a7af6e8ed2ab39557fc
Author: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Date: Sun Nov 1 09:15:32 2026 +0000
d/scripts/qcom-va-driver-tests: save the output of each test
The test output was only printed to the terminal, so errors from tests
that do not write their own logs and the final summary were lost once
the terminal was closed, even though the results directory is meant to
be kept for inspection.
Save the output of each test to its own log file and the complete
output of the run, including warnings and the summary, to output.log
in the results directory.
Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Among the 2 debian patches available in version 1.1.0-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/q/qcom-va-driver.png){kind=link}