Thanks for the patch!
The merged upstream patch is in chromium v105, but it's not in v104
(which is what we're currently on). v105 is slated for release on Aug 30th.
I'll will try including your patch in the v105 upload, at least for sid.
Since it depends on kernel 5.17 headers, I'm not yet sure what to do
about bullseye.
On 8/12/22 02:57, Eschenbacher.Stefan wrote:
On June 24 the Linux Mainline V4L2 stateless patch was merged.
media/gpu/v4l2: Split upstream compatible and ChromeOS specific code
(Iff3c2a53) · Gerrit Code Review (googlesource.com)
<https://chromium-review.googlesource.com/c/chromium/src/+/3380426>
-Without this patch there was only v4l2 stateless support for Chrome OS
-“use_vaapi=true” and “use_v4l2_codec=true” cannot be enabled at the
same time. According to patch author Chen-Yu Tsai VA-API is for x86
platforms and v4l2 is for arm platforms.
The file “rules” must be patched to enable v4l2 and disable vaapi for
arm devices:
--- /home/stefan/rules.old 2022-08-12 08:50:21.527565964 +0200
+++ /home/stefan/rules.new 2022-08-12 08:51:18.733269432 +0200
@@ -52,10 +52,10 @@
defines+=host_cpu=\"x64\" use_vaapi=true
endif
ifeq (arm64,$(DEB_HOST_ARCH))
-defines+=host_cpu=\"arm64\" use_vaapi=true
+defines+=host_cpu=\"arm64\" use_v4l2_codec=true use_vaapi=false
endif
ifeq (armhf,$(DEB_HOST_ARCH))
-defines+=host_cpu=\"arm\" use_vaapi=false arm_use_neon=false
+defines+=host_cpu=\"arm\" use_v4l2_codec=true use_vaapi=false
arm_use_neon=false
endif
# disabled features
