According to this post the Vivante GPU should be OpenGL 2.1 capable: https://lists.yoctoproject.org/pipermail/meta-freescale/2013-August/004484.html Unfortunately, while libGL.so is present in gpu binary drivers, build headers are not present neither in gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-sfp.bin nor in gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-hfp.bin. Please provide /usr/include/GL folder with respective headers.
(In reply to comment #0) > According to this post the Vivante GPU should be OpenGL 2.1 capable: > https://lists.yoctoproject.org/pipermail/meta-freescale/2013-August/004484. > html > > Unfortunately, while libGL.so is present in gpu binary drivers, build > headers are not present neither in > gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-sfp.bin nor in > gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-hfp.bin. > > Please provide /usr/include/GL folder with respective headers. We've been using mesa GL headers; does it work for you?
(In reply to comment #1) > (In reply to comment #0) > > According to this post the Vivante GPU should be OpenGL 2.1 capable: > > https://lists.yoctoproject.org/pipermail/meta-freescale/2013-August/004484. > > html > > > > Unfortunately, while libGL.so is present in gpu binary drivers, build > > headers are not present neither in > > gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-sfp.bin nor in > > gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-hfp.bin. > > > > Please provide /usr/include/GL folder with respective headers. > > We've been using mesa GL headers; does it work for you? I've tried copying manually GL headers from a Mesa version, but I think they were from a 8.0.x version. I've successfully built Panda3D framework with it but had "Segmentation fault" problems I didn't had on OpenGL ES. I'll try with Yocto's libgl-mesa-dev-9.1.6-r0.nitrogen6x.rpm and see if anything changes.
(In reply to comment #2) > I'll try with Yocto's > libgl-mesa-dev-9.1.6-r0.nitrogen6x.rpm and see if anything changes. One application segfaulting when built against Mesa OpenGL headers is Panda3D (see bug #5119)
*** Bug 5119 has been marked as a duplicate of this bug. ***
This is not going to be changed as this comes this way from the vendor.