chromium GPU acceleration doesn't work on imx6

[bmx666]

I created issue on meta-freescale - Freescale/meta-freescale#1203 before, but our team tested builds and found issue in new version of Chromium

[bmx666]

same issue with new version - 105.0.5195.102

[bmx666]

chrome://gpu doesn't displaySkia Renderer: Enabled anymore

[bmx666]

Since 104.0.5112.101 build configuration file out/Release/args.gn include by default angle_use_wayland = false. After change it back to angle_use_wayland = true build with clang-15 returns an error related to Chromium subrepo https://github.com/abseil/abseil-cpp and not yet included patches in Chromium version 105.0.5195.102 - abseil/abseil-cpp@0c92330 and abseil/abseil-cpp@cfe27e7 . Also Chromium subrepo angle has error during build of wayland, patch to fix that can be found here - https://bugs.chromium.org/p/angleproject/issues/detail?id=7582#c3

[MastaG]

Thanks for the fixes!

[bmx666]

I successfully built Chromium 108.0.5309.0, only few fixes are required since 105.0.5195.102:

• remove patch 0012-Build-X11-parts-only-for-ozone_platform_x11.patch because it already included
• update md5 hash of licenses
• patch third_party/wayland/src from upstream/1.19.0 to upstream/1.20.0 otherwise a lot of errors during compilation. Patch can be generated from wayland repo
• angle patch is not required anymore
• GN_ARGS += " angle_use_wayland=true use_qt=false use_system_libffi=true "

My major issue - GPU acceleration still doesn't work

[bmx666]

Tested Chromium 104.0.5112.0 - GPU acceleration doesn't work.
A lot of changes between 103 and 104...

[MastaG]

Well I did a few tests on my ODroid XU4 which is armv7 (32bits).
It uses the Mesa Panforst driver and runs on Gnome 42 wayland.
For me the problem is that I can only run it with "--in-process-gpu" otherwise it seems to segfault.

I've rebuilt chromium-ozone-wayland 105.0.5195.102 with the angle patch: https://bugs.chromium.org/p/angleproject/issues/detail?id=7582#c3 and angle_use_wayland = true
But that doesn't seem to make a difference, what does Angle do anyways? It seems to make the binary a lot bigger.

These are the parameters for making it run on my GPU:
--use-gl=egl --ozone-platform=wayland --in-process-gpu --reduce-gpu-sandbox --gpu-sandbox-start-early --ignore-gpu-blocklist --ignore-gpu-blacklist --enable-gpu-rasterization --enable-features=RawDraw,CanvasOopRasterization,WebRTCPipeWireCapturer

[bmx666]

Hi @MastaG

I'm launching chromium with flags --use-gl=egl --ozone-platform=wayland --enable-gpu --enable-gpu-rasterization --enable-gpu-memory-buffer-video-frames --enable-accelerated-2d-canvas --enable-accelerated-vpx-decode --enable-native-gpu-memory-buffers --enable-zero-copy --gpu-no-context-lost --ignore-gpu-blacklist --in-process-gpu

I can try to add flags --reduce-gpu-sandbox --gpu-sandbox-start-early --ignore-gpu-blocklist --enable-gpu-rasterization --enable-features=RawDraw,CanvasOopRasterization,WebRTCPipeWireCapturer and check with version 105

[bmx666]

what does Angle do anyways?

About ANGLE ->
https://chromium.googlesource.com/angle/angle/+/master/README.md
https://chromium.googlesource.com/angle/angle/+/refs/heads/main/doc/BuildingAngleForChromiumDevelopment.md

[bmx666]

I build version 103, but with DEPS from version 104

-  'skia_revision': 'b301ff025004c9cd82816c86c547588e6c24b466',
+  'skia_revision': '5a4dbb2e97302f7e574f0ba962ac4d8b3a62a36e',

-  'angle_revision': '53e1711046b815dfff3321c3027f190c9b0b899b',
+  'angle_revision': '4a65a669e11bd7bfa9d77cbf7001836379ec29b5',

-  'swiftshader_revision': 'f1c2c0b0728152d7ca24472e696e07e957e6d09a',
+  'swiftshader_revision': 'd68d367047f562e0e0716fd72b9a2bc3e2c8f4c0',

-  'src/third_party/vulkan-deps': '{chromium_git}/vulkan-deps@c6a60f3cc711e0758ebb58d8d1db9f97b5973ccc',
+  'src/third_party/vulkan-deps': '{chromium_git}/vulkan-deps@12989fc8d7d273b5b95ef988d37469738eb9c39b',

   'src/third_party/webgl/src':
-    Var('chromium_git') + '/external/khronosgroup/webgl.git' + '@' + 'cf04aebdf9b53bb2853f22a81465688daf879ec6',
+    Var('chromium_git') + '/external/khronosgroup/webgl.git' + '@' + 'bb289ce3cb15bbabd42fdcb01439367846d9069d',

   'src/third_party/webgpu-cts/src':
-    Var('chromium_git') + '/external/github.com/gpuweb/cts.git' + '@' + 'b32ac31a0eab7386807f01c7cb8d77a6e1104c23',
+    Var('chromium_git') + '/external/github.com/gpuweb/cts.git' + '@' + '84183b561b7f44b2eae6a5f268d5085accb0ad7a',

And GPU acceleration still works fine.

Major difference between 103 and 104:

-  'src/third_party/glfw/src':
-    Var('chromium_git') + '/external/github.com/glfw/glfw.git@' +  '94773111300fee0453844a4c9407af7e880b4df8',
-

   'src-internal': {
-    'url': 'https://chrome-internal.googlesource.com/chrome/src-internal.git@2abd00903939dc3d89433d476402b4ebb6ee982d',
+    'url': 'https://chrome-internal.googlesource.com/chrome/src-internal.git@6956112deae1e1529cc3fe8eb3112e60c5104b58',

[bmx666]

since Chromium 108.0.5317.0 DEPS wayland was updated to version upstream/1.20.0

pushed into my fork -> https://github.com/bmx666/ossystems-meta-browser

[bmx666]

on i.MX6 Chromium 103.0.5060.129 only these extra flags enables most of all HW acceleration features

--in-process-gpu --enable-features=RawDraw,CanvasOopRasterization --enable-gpu-rasterization --num-raster-threads=4 --enable-zero-copy

[MastaG]

Try adding:
--reduce-gpu-sandbox --gpu-sandbox-start-early --ignore-gpu-blocklist --ignore-gpu-blacklist

[bmx666]

@MastaG no luck, I've tried all the argument options since version 104 and later... Chromium doesn't have GPU rasterization on imx6, everything is slow and laggy...