When I switching from fKMS to Legacy non-GL driver (that's providing hardware accelerated OpenGL ES but software OpenGL), the Chromium browser is now using llvmpipe, not hardware accelerated OpenGL ES. If I set --use-gl=egl parameter, nothing changes. I see that Chromium uses libGLESv2.so.2 from the Mesa package, that's becoming software if I use proprietary OpenGL ES. In my case, Chromium needs to use libGLESv2.so library, not *.so.2. Or libbrcmGLESv2.so.
If I remove libGLESv2.so.2 and make symlink to /opt/vc/lib/libbrcmGLESv2.so (and for EGL too), then I have this error:
It seems that the default Chromium build is depending of Mesa EGL, and cannot work with the Broadcom EGL. Is there a build that's linked with the Broadcom OpenGL ES and EGL?
Code: Select all
[4374:4374:1206/045723.497716:ERROR:gl_surface_egl.cc(943)] EGL display query failed with error EGL_SUCCESS [4374:4374:1206/045723.498296:ERROR:gl_surface_egl.cc(957)] eglInitialize Default failed with error EGL_BAD_DISPLAY [4374:4374:1206/045723.498442:ERROR:gl_initializer_x11.cc(154)] GLSurfaceEGL::InitializeOneOff failed. [4374:4374:1206/045723.517910:ERROR:viz_main_impl.cc(170)] Exiting GPU process due to errors during initialization