Closed MastaG closed 1 year ago
the chromium's v4l2vda has some special requirements, not for all v4l2mem devices.
the official one should be tegra.
for rockchip, i'm using a v4l2 plugin to wrap mpp apis to adapt to chromium's requirements: https://github.com/JeffyCN/libv4l-rkmpp#faq
the patches here, are just to enable the v4l2vda, you might need to enable debugging logs and make your own patch to adapt your driver(or in chromium, or make another v4l2 wrap plugin)
Hi JeffyCN,
I'm struggling a bit for while now to get the v4l2-m2m decoder to work with chromium-ozone-wayland. I've built it with your patchset on top of it. Then I'm running Chromium with:
--use-gl=egl --ozone-platform=wayland --in-process-gpu --no-sandbox --gpu-sandbox-start-early --ignore-gpu-blocklist --ignore-gpu-blacklist --enable-accelerated-video-decode --enable-features=VaapiVideoDecoder,VaapiVideoEncoder
When I go to the chrome://gpu patch it says:
I do have symlinks created for my video encoder and decoder:
But when I play a video from youtube with h264ify enabled it always seems to select ffmpeg:
Log:
Any ideas? Kodi is working fine with FFMPeg's v4l2m2m decoder.