summaryrefslogtreecommitdiffstats
path: root/src/gallium/docs
diff options
context:
space:
mode:
authorErik Faye-Lund <[email protected]>2019-07-05 16:21:45 +0200
committerErik Faye-Lund <[email protected]>2019-07-10 15:49:57 +0200
commit21de1bf24ba6d65f1566c3b8b742636587c39697 (patch)
treedc5d76ceedbb1fb3823650bc219f78ac013014af /src/gallium/docs
parent681fa03e8d290ab1ee49de3f2c35f3dbb11636dc (diff)
gallium: give vertex-shader saturate its own cap
Shader Model 3.0 is a big promise to make to the state-tracker, and for instance mobile hardware might support vertex-shader saturate but not some of the other features of SM3. So let's give this its own cap for simplicity. Signed-off-by: Erik Faye-Lund <[email protected]> Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/docs')
-rw-r--r--src/gallium/docs/source/screen.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst
index 01072581883..1f1728d717a 100644
--- a/src/gallium/docs/source/screen.rst
+++ b/src/gallium/docs/source/screen.rst
@@ -538,6 +538,8 @@ The integer capabilities:
explicit LOD is supported in the fragment shader.
* ``PIPE_CAP_FRAGMENT_SHADER_DERIVATIVES``: True if the driver supports
derivatives in fragment shaders.
+* ``PIPE_CAP_VERTEX_SHADER_SATURATE``: True if the driver supports saturate
+ modifiers in the vertex shader.
.. _pipe_capf: