Aaron Brice

We have been stuck on chromium 92 on i.MX8QM for a while but I copied this recipe from NXP's meta-imx layer: https://github.com/nxp-imx/meta-imx/tree/langdale-6.1.1-1.0.0/meta-sdk/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/ Seems to work, with GPU acceleration, gets us...

I haven't tried hardware video decode but a commit says it was added: commit fe0d3587d905a8fa32a9830d177f97c90352fdc5 Author: Hou Qi Date: Thu Sep 15 22:28:13 2022 +0800 chromium-ozone-wayland: Add V4L2VDA support on...

Yes, available at https://github.com/nxp-imx/meta-imx/tree/langdale-6.1.1-1.0.0/meta-sdk/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/

If I run chromium without --in-process-gpu, the SVG images display correctly (but no HW accel). Does SVG rendering use the GPU? Is there a flag to force software rendering of...

More narrowly, if I run --in-process-gpu --disable-gpu-rasterization then SVGs display ok. So something in GPU rasterization in chromium 101 on i.MX8QM vivante GPU is causing problems for SVG image rendering.

@steven-smpct I am also getting this dri configure error on an i.MX8 building chromium-ozone-wayland. Can you give me more details on your fix? Previously the workaround was to add mesa...