On Thu, 2018-11-15 at 13:45 +0100, Gert Wollny wrote: > From: Gert Wollny <gert.wol...@collabora.com> > > Dear all, > > after the RFC and Ilias comments I reworked the series another > time. > Changes with respect to the RFC are > - renaming the new CAP > - reordering of the patches that no double checking of > EXT_sRGB and EXT_framebuffer_sRGB is needed. > > thanks for reviewing, > Gert > > Gert Wollny (8): > Gallium: Add new CAPS to indicate whether a driver can switch SRGB > write > virgl: Set sRGB write control CAP based on host capabilities > mesa:main: Add flag for EXT_sRGB to gl_extensions > i965: Set flag for EXT_sRGB > mesa/st: rework support for sRGB framebuffer attachements > mesa/main: Use flag for EXT_sRGB instead of EXT_framebuffer_sRGB > where > possible > mesa/main/version: Lower the requirements for GLES 3.0 > mesa/main: Expose EXT_sRGB_write_control >
Hmm. So you only add a driver cap for EXT_sRGB, you don't actually expose the extension, right? I can't see it added to extensions_table.h... Is there a reason for that? I guess it's more work than you'd want, considering it requires stuff like disallowing glGenerateMipmap() with sRGB textures... _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
