[meta-freescale] BSP 1.1.0 vs. OpenGL ES2.0/Qt5
Thomas Senyk
thomas.senyk at pelagicore.com
Tue Feb 26 10:25:41 PST 2013
Hi,
I think it's time to start a independent thread about (my) inability to get
anything OpenGL ES2.0 related running on the new BSP (aka.: "[PATCH v4 0/9]
iMX6Q BSP 1.1.0 upgrade")
fyi: I'm always building without 'x11' in DISTRO_FEATURES
My findings so far:
1. Someone mentioned that it's possible to deploy/unpack the 1.1.0 drivers on
top of a 12.04.01-image and still run Qt5.
I can confirm this!
This means it's NOT the libraries (aka. driver?) which are causing this
problem!
(From here on everything is based on a "PATCHv4"-build!)
2. I can't get any of the viv_samples running!
Their behavior is rather erratic
(sometimes errors and crashes, something just black screen nothing on stdout)
... I guess it's because they "pollute" the drivers-state if they crash...
Anyway: Very often I get errors like:
VertexShader: chiclet.vert: comiple error
FragmentShader: chiclet.frag: comiple error
ShaderProgram: null vertex program
Segmentation fault
.. which look very similar to the Qt errors I have:
QOpenGLShader::compile(Vertex): failed
Problematic Vertex shader source code ***
attribute mediump vec4 vertexCoord;
attribute mediump vec4 vertexColor;
uniform mediump mat4 matrix;
uniform mediump float opacity;
varying lowp vec4 color;
void main() {
gl_Position = matrix * vertexCoord;
color = vertexColor * opacity;
}
Can anyone confirm or contradict* this?
*can you build a image bases on the PATCHv4, and any of viv_samples (which use
es2.0) on the screen?
3. It's not because of former "highp"-error (I replaced all 'highp' within the
Qt code with 'mediump')
... The next thing I'll do is build without PATCHv4 ... as some patches have
already gone in (e.g. kernel) it might be that it's not about PATHv4, but
rather about the patches already in.
... I'll give a update tomorrow.
Greets
Thomas
More information about the meta-freescale
mailing list