Hi thank you for the help, I will test The only reason for trying to use the texture to wl_buffer directly was just to get something working and then work back from there to see if it was an application side issue or not.
Also just a fun experiment. On Sun, Mar 29, 2015 at 6:04 AM, Jason Ekstrand <ja...@jlekstrand.net> wrote: > On Sat, Mar 28, 2015 at 6:57 AM, x414e54 <x414...@linux.com> wrote: > > > I was originally blitting the texture to the default framebuffer and then > > trying to use eglSwapBuffers. But for some reason eglSwapBuffers was > > returning EGL_BAD_SURFACE even though eglMakeCurrent had no errors. > > Can you render to it? That sounds like something is wrong in the way > you're setting up your EGLSurface. Of you can render you should be able to > blit. > --Jason > If I call eglSwapBuffers just after the context creation it works fine and the buffer is committed to the Wayland surface. Making the context current and performing the glBlit also works fine (tested using glReadPixels). eglQuerySurface also seems to work fine. However eglSwapInterval and eglSwapBuffers returns EGL_BAD_CONTEXT and EGL_BAD_SURFACE respectively. The code is run all in one function and during a mutex to prevent the context becoming current on another thread.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
