GLESv2: what stencil/depth combinations should work?

[Hexxeh]

As per issue title. I'm trying to get Chrome running on the Pi with acceleration by adding the dispmanx specific stuff into Chrome's code as a bit of a hack until we have a better way of doing things, but I'm seeing these errors:

[2020:2020:92746901:ERROR:gles2_cmd_decoder.cc(3031)] GLES2DecoderImpl::ResizeOffscreenFrameBuffer failed because offscreen FBO was incomplete.
[2020:2020:92748510:ERROR:gles2_cmd_decoder.cc(2211)] Could not allocate offscreen buffer storage.
[1996:1996:92759790:ERROR:command_buffer_proxy_impl.cc(134)] Failed to initialize command buffer service.
[1996:1996:92773044:FATAL:image_transport_factory.cc(377)] Failed to make compositor shared context current.

I've asked some of the Chrome devs, and they've suggested I ask whoever wrote the GLESv2 implementation what stencil/depth combinations should work, as apparently this would save me a hell of a lot of time.

The appropriate bit of the Chrome code is here, I think: http://code.google.com/searchframe#OAMlx_jo-ck/src/gpu/command_buffer/service/gles2_cmd_decoder.cc&type=cs&l=2116

I've not really touched GL/GLES/EGL before, so I'm just stabbing in the dark based on triangle.c, so if I'm on completely the wrong track, then apologies for wasting your time... :)

[raspberrypi]

GL_DEPTH24_STENCIL8 should definitely work on VideoCore IV.

On Thu, May 17, 2012 at 1:36 AM, Liam McLoughlin
[email protected]
wrote:

As per issue title. I'm trying to get Chrome running on the Pi with acceleration by adding the dispmanx specific stuff into Chrome's code as a bit of a hack until we have a better way of doing things, but I'm seeing these errors:

[2020:2020:92746901:ERROR:gles2_cmd_decoder.cc(3031)] GLES2DecoderImpl::ResizeOffscreenFrameBuffer failed because offscreen FBO was incomplete.
[2020:2020:92748510:ERROR:gles2_cmd_decoder.cc(2211)] Could not allocate offscreen buffer storage.
[1996:1996:92759790:ERROR:command_buffer_proxy_impl.cc(134)] Failed to initialize command buffer service.
[1996:1996:92773044:FATAL:image_transport_factory.cc(377)] Failed to make compositor shared context current.

I've asked some of the Chrome devs, and they've suggested I ask whoever wrote the GLESv2 implementation what stencil/depth combinations should work, as apparently this would save me a hell of a lot of time.

The appropriate bit of the Chrome code is here, I think: http://code.google.com/searchframe#OAMlx_jo-ck/src/gpu/command_buffer/service/gles2_cmd_decoder.cc&type=cs&l=2116

I've not really touched GL/GLES/EGL before, so I'm just stabbing in the dark based on triangle.c, so if I'm on completely the wrong track, then apologies for wasting your time... :)

---

Reply to this email directly or view it on GitHub:
#20

[popcornmix]

A bit more from our GL guy:
I think Eben's being a bit keen with "GL_DEPTH24_STENCIL8 should definitely work on VideoCore IV."
The hardware certainly supports packed depth24/stencil8 – that's in fact the native depth/stencil format. However, that's a GLES2 extension AFAICT (GL_OES_packed_depth_stencil) and we don't appear to implement it.
I think you might have success with using DEPTH=16 & STENCIL=NONE or DEPTH=24 & STENCIL=8 but it doesn't look like the driver will accept DEPTH=16 & STENCIL=8.
It looks like the linked code will try to use DEPTH=16 & STENCIL=8.

[popcornmix]

This is not something we are in a position to support with the current driver.