Open Embedded OpenGL ES 3.0 support


#1

I am trying to get OpenGL ES v3.0 support working on a yocto build. I was not able to get it working on my custom build, so I tried the builds provided by liarno. The provided images also show ES 2.0 for openembedded images.

Debian 17.06 supports Mesa 13.0.6 and ES 3.0, but yocto has Mesa 17.1.1 and ES 2.0.

Is this a known issue? Is there a way to configure append the mesa recipe to enable ES 3.0?

Debian 17.06:

linaro@linaro-alip:~$ glxinfo | grep version
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 3.1
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.1 (Core Profile) Mesa 13.0.6
OpenGL core profile shading language version string: 1.40
OpenGL version string: 3.0 Mesa 13.0.6
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

OpenEmbedded 17.06.1 rpb desktop image:

root@dragonboard-410c:~# export DISPLAY=:0
root@dragonboard-410c:~# glxinfo | grep version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 17.1.1
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
root@dragonboard-410c:~#


#2

I went ahead and created a bug report. Here is the link

https://bugs.96boards.org/show_bug.cgi?id=571


#3

It would be interesting to have the ‘renderer string’ (filtered by your grep) in order to determine which driver is in use, maybe software rendering is used.

It would also be a big help to have the content of /var/log/Xorg.0.log to check what happens here.


#4

I’ve updated the bug report with the information you requested.