<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does." href="https://bugs.freedesktop.org/show_bug.cgi?id=102354#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does." href="https://bugs.freedesktop.org/show_bug.cgi?id=102354">bug 102354</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>(In reply to Deve from <a href="show_bug.cgi?id=102354#c16">comment #16</a>) > One thing that I noticed is that when you added new formats in > intel_screen.c, now it should be probably: > > if (intel_loader_get_cap(dri_screen, DRI_LOADER_CAP_RGBA_ORDERING)) > num_formats = ARRAY_SIZE(formats); > else > num_formats = 5; > > rather than num_formats = 3. At least for me > intel_loader_get_cap(dri_screen, DRI_LOADER_CAP_RGBA_ORDERING) returns false. > > In this case I see quite a lot configs with modes->sRGBCapable = true in > driCreateConfigs in utils.c, but still no srgb-capable format in glxinfo :( Yep, that is a clear bug in the patch. With the change I get even more configs/visuals that have srgb set to 's'. Will debug some more.</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>