<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - virgl on OpenGL 3.3 host regressed to OpenGL 2.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=110921#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - virgl on OpenGL 3.3 host regressed to OpenGL 2.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=110921">bug 110921</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Looks like ARB_framebuffer_sRGB is not provided for some reason by virgl. There was recently reworked in virgl to try to be more precise, esp in ES, and I suspect something here ended up as a casualty... extensions->EXT_framebuffer_sRGB = screen->get_param(screen, PIPE_CAP_DEST_SURFACE_SRGB_CONTROL) && extensions->EXT_sRGB; Where EXT_sRGB is controlled by: { { o(EXT_sRGB) }, { PIPE_FORMAT_A8B8G8R8_SRGB, PIPE_FORMAT_B8G8R8A8_SRGB, PIPE_FORMAT_R8G8B8A8_SRGB }, GL_TRUE }, /* at least one format must be supported */ And the cap is controlled by: case PIPE_CAP_DEST_SURFACE_SRGB_CONTROL: return vscreen->caps.caps.v2.capability_bits & VIRGL_CAP_SRGB_WRITE_CONTROL; Probably one or both of those is false for some silly reason. Could even be due to an older version of the virgl "server" component which doesn't include that capability bit.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>