(In reply to Leo_sk from comment #14) Then I think it's harmless and the desired behavior: EGL/OGL 2.1 is not enough (bug 1474281), so it falls back to EGL/GLES 3.1 (bug 1654700): https://www.raspberrypi.org/blog/vc4-and-v3d-opengl-drivers-for-raspberry-pi-an-update/ > At present, the V3D driver exposes OpenGL ES 3.0 and OpenGL 2.1. As I mentioned above, the VideoCore VI GPU can do OpenGL ES 3.2, but it can’t do OpenGL 3.0, so future feature work will focus on OpenGL ES. > The other big piece of work we have been tackling, and that we are very excited about, is OpenGL ES 3.1, which will bring Compute Shaders to Raspberry Pi 4! Credit for this goes to Eric Anholt, who did all the implementation work before leaving In comparison, GLX is not capable of falling back to something else, therefore I assume you can't get WebRender without MOZ_X11_EGL=1. These "can't find symbol" errors are unrelated to Raspberry Pi. Can you [file](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) a separate bug about Raspberry PI 4 WebRender performance? Thanks! (In reply to Martin Stránský [:stransky] from comment #12) > Also firefox window has visual artifacts and video playback shows error: > "Failed to create scanout resource. > drmPrimeFDToHandle() failed: Cannot allocate memory" > > Let's see if Bug 1650583 fixes that. drm is not used in Firefox itself when HW acceleration is disabled (the "Failed to create EGLContext!" message). WebRender is working fine according to about:support. Raspberry Pi doesn't support VAAPI. * https://trac.ffmpeg.org/wiki/HWAccelIntro Google: "[Raspi DMABUF MMAL](https://www.google.com/search?q=raspi+dmabuf+mmal+site:www.raspberrypi.org&client=firefox-b-d&sa=X&ved=2ahUKEwj2jL3h38frAhUJNOwKHengAywQrQIoBHoECAcQBQ&biw=1246&bih=1326)" - It's something on top of Video4Linux, but it sounds like V4L2 could be used directly on Raspi4, I don't know. Let's file a new bug about hw video decoding on Raspi. * drmPrimeFDToHandle [would be used](https://www.raspberrypi.org/forums/viewtopic.php?p=1648222#p1648222) as well, but "[GBM is broken right now on RPI4 v3d video drivers](https://github.com/raspberrypi/linux/issues/3411)": https://github.com/lgsvl/meta-lgsvl-browser/commit/282c2b24b604b7ab88c1904eafb17aff75e9ccac
Bug 1661359 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Leo_sk from comment #14) Then I think it's harmless and the desired behavior: EGL/OGL 2.1 is not enough (bug 1474281), so it falls back to EGL/GLES 3.1 (bug 1654700): https://www.raspberrypi.org/blog/vc4-and-v3d-opengl-drivers-for-raspberry-pi-an-update/ > At present, the V3D driver exposes OpenGL ES 3.0 and OpenGL 2.1. As I mentioned above, the VideoCore VI GPU can do OpenGL ES 3.2, but it can’t do OpenGL 3.0, so future feature work will focus on OpenGL ES. > The other big piece of work we have been tackling, and that we are very excited about, is OpenGL ES 3.1, which will bring Compute Shaders to Raspberry Pi 4! Credit for this goes to Eric Anholt, who did all the implementation work before leaving In comparison, GLX is not capable of falling back to something else, therefore I assume you can't get WebRender without MOZ_X11_EGL=1. These "can't find symbol" errors are unrelated to Raspberry Pi. Can you [file](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) a separate bug about Raspberry PI 4 WebRender performance? Thanks! (In reply to Martin Stránský [:stransky] from comment #12) > Also firefox window has visual artifacts and video playback shows error: > "Failed to create scanout resource. > drmPrimeFDToHandle() failed: Cannot allocate memory" > > Let's see if Bug 1650583 fixes that. drm is not used in Firefox itself when HW acceleration is disabled (the "Failed to create EGLContext!" message). WebRender is working fine according to about:support. Raspberry Pi doesn't support VAAPI. * https://trac.ffmpeg.org/wiki/HWAccelIntro Google: "[Raspi DMABUF MMAL](https://www.google.com/search?q=raspi+dmabuf+mmal+site:www.raspberrypi.org&client=firefox-b-d&sa=X&ved=2ahUKEwj2jL3h38frAhUJNOwKHengAywQrQIoBHoECAcQBQ&biw=1246&bih=1326)" - It's something on top of Video4Linux (?), but it sounds like V4L2 could be used directly on Raspi4, I don't know. Let's file a new bug about hw video decoding on Raspi. * drmPrimeFDToHandle [would be used](https://www.raspberrypi.org/forums/viewtopic.php?p=1648222#p1648222) as well, but "[GBM is broken right now on RPI4 v3d video drivers](https://github.com/raspberrypi/linux/issues/3411)": https://github.com/lgsvl/meta-lgsvl-browser/commit/282c2b24b604b7ab88c1904eafb17aff75e9ccac