Your message dated Thu, 29 Oct 2026 11:01:25 +0000
with message-id <[email protected]>
and subject line Bug#1152234: fixed in qcom-va-driver 1.1.0-1
has caused the Debian Bug report #1152234,
regarding ITP: qcom-va-driver -- VA-API driver for Qualcomm Iris V4L2 devices
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1152234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1152234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Christopher Obbard <[email protected]>
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
* Package name : qcom-va-driver
Version : 1.1.0
Upstream Contact: Xilin Wu <[email protected]>
* URL : https://github.com/radxa-pkg/qcom-va-driver
* License : Expat
Programming Lang: C++, C
Description : VA-API driver for Qualcomm Iris V4L2 devices
This experimental driver provides hardware-accelerated video decoding
and H.264/HEVC encoding through the Qualcomm Iris stateful V4L2
memory-to-memory interface.
.
Supported decoding: H.264 (Constrained Baseline, Main, High), HEVC
(Main, Main10), VP9 (profiles 0 and 2) and AV1 (Main, where exposed
by the hardware). Supported encoding: H.264 and HEVC Main (8-bit).
Optional Vulkan-based video processing provides scaling, cropping,
rotation, format conversion, overlays and HDR10 to SDR tone mapping.
Why is this package useful?
Qualcomm SoCs with the Iris video block (e.g. SC8280XP, X1E80100) have
an upstream stateful V4L2 driver in Linux, but most applications (e.g.
FFmpeg, GStreamer va plugin, mpv, VLC, Chromium, Kodi) use hardware
video acceleration through VA-API. This driver bridges the two so those
applications can decode and encode in hardware on these
platforms. Upstream has tested it on SC8280XP (Radxa Dragon Q8B) and
I have tested it on X1E80100 (Snapdragon X Elite).
There is no existing VA-API backend for this hardware in Debian. It is
not a generic V4L2 backend and is targeted specifically at Iris; the
project was previously named libva-v4l2.
Packaging notes:
- Built for arm64 only, with the GPU (EGL/GLES/GBM) surface copy and
Vulkan VPP backends enabled.
- The CDSP VPP backend is disabled, as it needs toolchains downloaded
at build time and Qualcomm Hexagon SDK components; the package has
no non-free build or runtime dependencies and targets main.
- The driver is installed as qcom_drv_video.so. The upstream
system-wide environment snippets (/etc/profile.d,
environment.d) that force GST_VA_ALL_DRIVERS and change GStreamer
element ranks are not shipped; README.Debian documents how to set
them manually instead.
- Some features need Iris kernel patches that are carried in the
upstream repository and are not yet in mainline Linux (decode-order
output, larger capture pools, encoder deblocking controls, error
timestamps, NOSHOW buffer recycling for AV1). This is documented
in README.Debian and upstream is actively working on upstreaming the
patches; this requirement will go away soon and will work with a
vanilla Debian kernel.
- The hardware regression tests are shipped in a separate
qcom-va-driver-tests binary package under /usr/libexec.
Maintenance:
I plan to maintain this within the Debian Multimedia Maintainers team,
alongside libva and the other VA-API drivers, with myself as Uploader.
Packaging will live at:
https://salsa.debian.org/multimedia-team/qcom-va-driver
I am a Debian Developer and will upload it myself. I have access to
the supported hardware for testing.
--- End Message ---
--- Begin Message ---
Source: qcom-va-driver
Source-Version: 1.1.0-1
Done: Christopher Obbard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
qcom-va-driver, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christopher Obbard <[email protected]> (supplier of updated
qcom-va-driver package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 28 Oct 2026 21:12:04 +0000
Binary: qcom-va-driver qcom-va-driver-dbgsym qcom-va-driver-tests
qcom-va-driver-tests-dbgsym
Source: qcom-va-driver
Architecture: arm64 source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <[email protected]>
Changed-By: Christopher Obbard <[email protected]>
Closes: 1152234
Description:
qcom-va-driver - VA-API driver for Qualcomm Iris V4L2 devices
qcom-va-driver-tests - Hardware tests for the Qualcomm Iris V4L2 VA-API driver
Changes:
qcom-va-driver (1.1.0-1) unstable; urgency=medium
.
* Initial release. (Closes: #1152234)
Checksums-Sha1:
071041146dba74d337b882e0c610119dd5f3b16e 2430 qcom-va-driver_1.1.0-1.dsc
1baaf5ab5d6abb6b3ae84499c1718f324816bbe9 180111
qcom-va-driver_1.1.0.orig.tar.gz
af460a322bf96dd763a18fecc4af488d8a2c7640 10996
qcom-va-driver_1.1.0-1.debian.tar.xz
c9e5f7ad10d5f77035e4a48967fcf46315e08ee8 8790
qcom-va-driver_1.1.0-1_source.buildinfo
bebb32f13e82642399e6df901daaa17df174b1e5 2277756
qcom-va-driver-dbgsym_1.1.0-1_arm64.deb
92edc0b33f66b35a40286652d4c444eeaad9c208 536976
qcom-va-driver-tests-dbgsym_1.1.0-1_arm64.deb
75b597c8e7d990b9bfb80bf495230ac84fb9ce29 74264
qcom-va-driver-tests_1.1.0-1_arm64.deb
8a71dbce08dfb50d529860a5de18b38ed7e67b2f 11910
qcom-va-driver_1.1.0-1_arm64.buildinfo
2a2c22ce1c6363a417ed57b80ac3b6b5382298c2 167028
qcom-va-driver_1.1.0-1_arm64.deb
Checksums-Sha256:
fc40963640f316f9bfc6fbdd10ea639fd3220060b75671d07f44a1098da8ce4a 2430
qcom-va-driver_1.1.0-1.dsc
92b3bc6e53a91735484770db77654c90d5f4506f2c194723e1fd7ce74ba65992 180111
qcom-va-driver_1.1.0.orig.tar.gz
a2cbcf5a203b79ef25c77823fcd20275f71e71f62cfd3a8678ac988dc0cd3b03 10996
qcom-va-driver_1.1.0-1.debian.tar.xz
4d5fdae8a1b03e2bc59d896650518b6f4be6f77c32e5405ff84163be40aae7ee 8790
qcom-va-driver_1.1.0-1_source.buildinfo
e70c03aa775e9dab018773167c28d69d32cd1c170d20a93adfa15780d5a541a1 2277756
qcom-va-driver-dbgsym_1.1.0-1_arm64.deb
ccc94abc824c5e2a61d91d4220951291a68b6b593c29076b39aaace98a131a2d 536976
qcom-va-driver-tests-dbgsym_1.1.0-1_arm64.deb
d014cfa615e2c991b8d3f76f9b0fdae09aeeee74356a31db0a704e4f951b53d8 74264
qcom-va-driver-tests_1.1.0-1_arm64.deb
d36aa8a79d0fb83ea63d267b8455796a2d1d3b1d284f6d91de97f560f56cd597 11910
qcom-va-driver_1.1.0-1_arm64.buildinfo
5917eb3ee57d479f659179f54d01d9ba371933a62f7a3abd23300665bb90879d 167028
qcom-va-driver_1.1.0-1_arm64.deb
Files:
e0700ad2b02faf9fd653eaae0feebab4 2430 video optional qcom-va-driver_1.1.0-1.dsc
161cb85bb7a2fb820823d8cbee9b1ce6 180111 video optional
qcom-va-driver_1.1.0.orig.tar.gz
a96bb1c0ea6f575dea339766dd6862b5 10996 video optional
qcom-va-driver_1.1.0-1.debian.tar.xz
fa2467df65aa32fb5f69769d3ba36d6b 8790 video optional
qcom-va-driver_1.1.0-1_source.buildinfo
b23af23731e5dce605c34fc1ba9ecd25 2277756 debug optional
qcom-va-driver-dbgsym_1.1.0-1_arm64.deb
66d080b437f5aa42338b1d33b5bdc0ba 536976 debug optional
qcom-va-driver-tests-dbgsym_1.1.0-1_arm64.deb
402ad2277c580f9ebaca143f0fc5f5a0 74264 video optional
qcom-va-driver-tests_1.1.0-1_arm64.deb
023f99c3b703ad8709dd15ea47fff54b 11910 video optional
qcom-va-driver_1.1.0-1_arm64.buildinfo
fef79fc45c9a06c039b859dce1c8bfde 167028 video optional
qcom-va-driver_1.1.0-1_arm64.deb
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE8Yvci2wl+QqiPVF0Y03E8GhwRvgFAmriewcACgkQY03E8Ghw
Rvjmrw/+PI6QSoHWRLNiQuG23i64ipA1Ad/QxZsND8PQno+xlq6HnK4OwkS1GIQI
L9QHIQqfVHiY+wwB2iwLShg8WFWjzRu312uLxtAKgT50JEovo53EplZDllYqGfZ5
SpWfXjNBV8D8bK8ndfLkz2NDVVb1KQ9+mnpnuAXEDfJ/ZttGknrnGlM2DB7IOs1b
QscXwYPpX5pSTHpMp5LpCwz959HeZoZq5TC+DSbbGSadphELEvXlFd0IRXT5hjgE
k10V2ctKDl7be7fFuGU358plLyXZEAnVnP8a3Ic409AuMSEdcxmQxq2SMqz7REHx
ZGC37SsHwXcas0n/I+CzPFMlZSKQ27Ia5gk0ErEXN7TfF3FpnK78u15+iPQzDr7P
IzuWeXTPbuKP08nglIIVJVj4WCzY8zodtfnhmfHDYJRZ+605ZKPFOWrOU2QzESWR
Rt60wMjU5RX/r7mi5DB5RIRUof+woXsxaJhHbffF87rPK9SR1UdWKh10nxwR2jUL
MR/Tv3lOfUKzaW6WAUWn+w0BPpmjUsPycSS/IdBxCIcE8ZVtJ/RoLawBzfGWkrOf
dSmldUeO/4Nx8NgAcrwZta8VhBYxKThUVjnB9GM6vKCtV/RLXd0tkkI7d9McLbek
BIs9RWg566DlbO5QE9NqQqCtpJIfButVWlN5wtX6oSzyFCy5MYc=
=mPXt
-----END PGP SIGNATURE-----
pgp1bLu57yApy.pgp
Description: PGP signature
--- End Message ---