aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/state_tracker/st_atom_array.c
diff options
context:
space:
mode:
authorKenneth Graunke <[email protected]>2016-08-02 11:04:01 -0700
committerKenneth Graunke <[email protected]>2016-08-08 14:01:51 -0700
commitcc27c7fe38dde3cfde30eb88dd5088b139d71f26 (patch)
treec8ea9b6108c6157d6368efb694cedc623282b5ef /src/mesa/state_tracker/st_atom_array.c
parentb1586526e84ab6eab2023b589da8e153f70dda50 (diff)
i965: Drop the "do resolves in sRGB" hack.
I've never quite understood the purpose of this hack - supposedly, doing resolves in the sRGB colorspace is slightly more accurate. Currently, BlitFramebuffer() ignores sRGB encoding and decoding on OpenGL, although it encodes and decodes in GLES 3.x. The updated OpenGL 4.4 rules also allow for encoding and decoding if GL_FRAMEBUFFER_SRGB is enabled, allowing the application to control what colorspace blits are done in. I don't think this hack makes any sense in such a world - the application can do what it wants, and we shouldn't second guess them. A related Piglit patch, "Make multisample accuracy test set GL_FRAMEBUFFER_SRGB when resolving." makes the Piglit MSAA accuracy test explicitly request SRGB encoding/decoding during resolves when running "srgb" subtests. Without that patch, this commit will regress those tests, but with it, they should continue to work just fine. Signed-off-by: Kenneth Graunke <[email protected]> Reviewed-by: Ian Romanick <[email protected]>
Diffstat (limited to 'src/mesa/state_tracker/st_atom_array.c')
0 files changed, 0 insertions, 0 deletions