The reason I prefer at the moment the way to change the order in the code is that there it is checked if the desktop implementation is an allowed choice. I do not know what the behavior would be if this is not a valid choice for some case but we use the command line flag.
The patch still allows to use "--use-gl=" in /etc/chromium.d/default-flags if people want to use something else for their installation. Best, Jan Am 09.01.21 um 08:03 schrieb Sedat Dilek: > Hi, > > Jan Luca is working on a patch "Use desktop gl implementation as default"... > > What about placing "--use-gl=desktop" in /etc/chromium.d/default-flags > as an alternative? > > # Default for GPU hardware-acceleration (Debian bug #979135) > export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --use-gl=desktop" > > Cannot say if this is wanted behaviour - to enable GPU hw-accel by default? > Looks like a safer methon when GPU hw-accel is wanted. > > In my logs I found references to Skia renderer... > > [ chrome://flags ] > > Skia API for compositing > If enabled, the display compositor will use Skia as the graphics API > instead of OpenGL ES. – Mac, Windows, Linux, Android > Here set to "Default" > > [ chrome://gpu ] > Graphics Feature Status > Skia Renderer: Enabled > > Cannot judge when not using ANGLE libs if there is a fallback to OpenGL ES. > Might be OpenGL ES renderer is the better choice? > > I have not looked for the parameters and cannot say I will play with them. > > ( BTW, I played with Vulkan support enabled - slow performance here > with Intel Sandy Bridge GPU. ) > > Regards, > - Sedat - > > [1] https://salsa.debian.org/janluca-guest/chromium/-/commits/angle_fix > [2] https://wiki.archlinux.org/index.php/chromium#Force_GPU_acceleration > [3] https://wiki.archlinux.org/index.php/chromium#Hardware_video_acceleration >
OpenPGP_signature
Description: OpenPGP digital signature
