Am Donnerstag, den 01.11.2018, 10:15 -0400 schrieb Ilia Mirkin: > So ... thinking about this a little more ... how is the new enable > different from the existing "EXT_framebuffer_sRGB" enable? When would > one be set but not the other?
This one is a GLES extension, there, if the surface attached to a framebuffer is sRGB capable, it behaves always like glEnable(GL_FRAMEBUFFER_SRGB) is set. With this extension, control is given back to the application. To keep compatibility, the default is still the same behaviour as without the extension (which is different from desktop GL). Best, Gert > On Thu, Nov 1, 2018 at 7:30 AM Gert Wollny <gw.foss...@gmail.com> > wrote: > > > > From: Gert Wollny <gert.wol...@collabora.com> > > > > Dear all, > > > > yet another update, only to the Gallium part: i.e. the format check > > was > > simplified according to Mareks comment, > > > > Best, > > Gert > > > > > > Gert Wollny (3): > > mesa/core: Add support for EXT_sRGB_write_control > > mesa/st: enable EXT_sRGB_write_control for Gallium drivers that > > support it > > intel/i965: Enable extension EXT_sRGB_write_control > > > > src/gallium/docs/source/screen.rst | 3 ++ > > src/mesa/drivers/dri/i965/intel_extensions.c | 1 + > > src/mesa/main/enable.c | 4 +-- > > src/mesa/main/extensions_table.h | 1 + > > src/mesa/main/get.c | 5 +++ > > src/mesa/main/get_hash_params.py | 1 + > > src/mesa/main/mtypes.h | 1 + > > src/mesa/state_tracker/st_extensions.c | 5 ++- > > src/mesa/state_tracker/st_manager.c | 37 ++++++++++++-- > > ------ > > 9 files changed, 41 insertions(+), 17 deletions(-) > > > > -- > > 2.18.1 > > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
