diff options
| author | Kenneth Graunke <kenneth@whitecape.org> | 2019-05-10 18:32:46 -0700 |
|---|---|---|
| committer | Kenneth Graunke <kenneth@whitecape.org> | 2019-05-14 19:34:29 -0700 |
| commit | c704c0226c15bd548489ab23ab8477c570edc69b (patch) | |
| tree | 7d3da0f9ea9a3cb6091c189b3bf33194942735a5 /src/gallium/docs/source/screen.rst | |
| parent | 4efd04ab182e7dad1d77f20ecdd03099330ea9f0 (diff) | |
gallium: Add a PIPE_CAP_FRAGMENT_SHADER_INTERLOCK.
Corresponding to GL_ARB_fragment_shader_interlock and
GL_NV_fragment_shader_interlock. Currently, only the NIR paths
support this functionality, but someone could conceivably add it
to TGSI too.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Diffstat (limited to 'src/gallium/docs/source/screen.rst')
| -rw-r--r-- | src/gallium/docs/source/screen.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index 1cf89eed2f9..c678ac91527 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -522,6 +522,8 @@ The integer capabilities: resource_from_handle and resource_get_handle. * ``PIPE_CAP_PREFER_COMPUTE_BLIT_FOR_MULTIMEDIA``: Whether VDPAU, VAAPI, and OpenMAX should use a compute-based blit instead of pipe_context::blit. +* ``PIPE_CAP_FRAGMENT_SHADER_INTERLOCK``: True if fragment shader interlock + functionality is supported. .. _pipe_capf: |