summaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorFrancisco Jerez <[email protected]>2016-07-21 20:32:12 -0700
committerFrancisco Jerez <[email protected]>2016-08-25 18:36:06 -0700
commit40b23ad57e8da0fd7af21e81ad52d615f9b492ed (patch)
treef47d1b986b54bd787dc60eb68e4affd4f929e6c4 /.mailmap
parent4a87e4ade778e56d43333c65a58752b15a00ce69 (diff)
i965/fs: Add brw_wm_prog_key bit specifying whether FB reads should be coherent.
Some of the following changes in this series are specific to the non-coherent path, so I need some way to tell whether the coherent or non-coherent path is in use. The flag defaults to the value of the gl_extensions::MESA_shader_framebuffer_fetch enable so that it can be overridden easily on hardware that supports both framebuffer fetch extensions in order to test the non-coherent path, like: MESA_EXTENSION_OVERRIDE=-GL_EXT_shader_framebuffer_fetch (Of course trying to force-enable the coherent framebuffer fetch extension on hardware without native support won't work and lead to assertion failures). Reviewed-by: Kenneth Graunke <[email protected]>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions