• Locked Locked
  • Replies 6 replies
  • Subscribers 137 subscribers
  • Views 7767 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mali T604 and eglImageKHR and FBO

Sebastien Baudouin
Note: This was originally posted on 12th June 2013 at http://forums.arm.com

Hi,

i'm implementing an Android application using the GPU and especially ImageKHR and FrameBuffer Objects.
In a thread and its GLES context i'm creating a texture and its eglImageKHR then i share the eglImageKHR handle with another thread. In this second thread i'm creating a FrameBuffer Object with the given eglImageKHR as color buffer and a renderbuffer (for the depth) . Then from this second thread i'm drawing using openGLES 1.x commands into the just created FBO. The result is displayed on screen by the First thread.

All that is working well with a MALI-400 but running that application on a nexus 10 which use MALI-T604 i have some issue.
1- NO GL ERROR appear.
2- the FBO status is OK

but the screen is sometime OK sometime completely black.

I try to replace the drawing operation by a simple clear color where the color is changing at each call and sometime i can see part of the screen with a color and part that is black.

Is someone aware of differences between MALI-400 and MALI-T604 that could cause such kind of issue. unfortunately i do not have any documentation on T604 to really understand what is happening. I tried to enable auto MIMAP generation in case of T604 as for (NVidia GPU it was a mandatory condition the make the texture "complete") but nothing has changed.

I suspect that it is coming from ImageKHR because i have a JAVA application where i'm uising FBO without ImageKHR and it seems to work fine.

Here is the sequence to create the FBO with EGLImageKHR:
glGenFramebuffersOES(1, (GLuint*) 0x777ada1c);
glBindFramebufferOES(GL_FRAMEBUFFER_OES, 1);

glGenRenderbuffersOES(1, (GLuint*) 0x777ada1c);
glBindRenderbufferOES(GL_RENDERBUFFER_OES, 1);

glRenderbufferStorageOES(GL_RENDERBUFFER_OES, GL_DEPTH_COMPONENT16_OES, 1184, 694);
glFramebufferRenderbufferOES(GL_FRAMEBUFFER_OES, GL_DEPTH_ATTACHMENT_OES, GL_RENDERBUFFER_OES, 1);

glGenTextures(1, (GLuint *) 0x777ada0c);
glBindTexture(GL_TEXTURE_2D, 3);
glEGLImageTargetTexture2DOES(GL_TEXTURE_2D, (GLeglImageOES) 0x752d700c);

glFramebufferTexture2DOES(GL_FRAMEBUFFER_OES, GL_COLOR_ATTACHMENT0_OES, GL_TEXTURE_2D, 3, 0);

glCheckFramebufferStatusOES(GL_FRAMEBUFFER_OES);



I hope someone will be able to help me to understand what i'm missing .

Br

Seb
Parents
  • Note: This was originally posted on 23rd July 2013 at http://forums.arm.com

    Hi McGeagh,

    Sorry to come back so lately to you.
    I still have the issue with my application. i definitively think there is an issue with FBO + Image KHR as my application is working fine when i'm not using FrameBuffer Object but instead using PBuffer plus glCopyTexSubImage2D.

    As said before when using FBO sometime i see a frame, sometime screen is black (most of the time).

    The working data path is as follow.
    1- Draw in a PBuffer
    2- copy data from PBuffer into a texture (tex1)using glCopyTexSubImage2D + glEGLImageTargetTexture2DOES as i'm using Image KHR .
    3- copy data from tex1 to tex2 using fbo bound onto tex 2
    4- display on screen tex2

    The path having issue.
    1- Create and Bind FBO using Image KHR  APIs onto tex 1
    2- Draw directly into tex1 thanks to FBO
    3- copy data from tex1 to tex2 using a second fbo bound onto tex 2
    4 -display on screen tex2

    For information i'm using eglCreateImageKHR with parameter EGL_GL_TEXTURE_2D_KHR is it still supported ?

    The problem is that both are working fine on Mali-400 and may other GPU but on MALI T604 (Nexus 10) 2nd path is not working and NO ERROR is reported.
    I tried to attach the Mali trace tool and no error is raised.

    Are you aware of such issue ? is there any workaround ?


    Any help is welcomed as now i'm stuck on possible investigation.


    Thanks in advance for you help.

    Seb


    Hello SebDoe,
    [color="#444444"] Do you have a reproducer app that we could test on our end?[/color]
    This will help us identify what the problem is, what the solution may be, and any workarounds that may be of use.

    Thanks in advance,

    McGeagh
Reply
  • Note: This was originally posted on 23rd July 2013 at http://forums.arm.com

    Hi McGeagh,

    Sorry to come back so lately to you.
    I still have the issue with my application. i definitively think there is an issue with FBO + Image KHR as my application is working fine when i'm not using FrameBuffer Object but instead using PBuffer plus glCopyTexSubImage2D.

    As said before when using FBO sometime i see a frame, sometime screen is black (most of the time).

    The working data path is as follow.
    1- Draw in a PBuffer
    2- copy data from PBuffer into a texture (tex1)using glCopyTexSubImage2D + glEGLImageTargetTexture2DOES as i'm using Image KHR .
    3- copy data from tex1 to tex2 using fbo bound onto tex 2
    4- display on screen tex2

    The path having issue.
    1- Create and Bind FBO using Image KHR  APIs onto tex 1
    2- Draw directly into tex1 thanks to FBO
    3- copy data from tex1 to tex2 using a second fbo bound onto tex 2
    4 -display on screen tex2

    For information i'm using eglCreateImageKHR with parameter EGL_GL_TEXTURE_2D_KHR is it still supported ?

    The problem is that both are working fine on Mali-400 and may other GPU but on MALI T604 (Nexus 10) 2nd path is not working and NO ERROR is reported.
    I tried to attach the Mali trace tool and no error is raised.

    Are you aware of such issue ? is there any workaround ?


    Any help is welcomed as now i'm stuck on possible investigation.


    Thanks in advance for you help.

    Seb


    Hello SebDoe,
    [color="#444444"] Do you have a reproducer app that we could test on our end?[/color]
    This will help us identify what the problem is, what the solution may be, and any workarounds that may be of use.

    Thanks in advance,

    McGeagh
Children
No data