summaryrefslogtreecommitdiffstats
path: root/src/gallium/docs/source/screen.rst
diff options
context:
space:
mode:
authorTimothy Arceri <[email protected]>2017-08-03 13:54:45 +1000
committerTimothy Arceri <[email protected]>2017-08-03 13:57:16 +1000
commit4e4042df6b8b9375ecabebd4dffeca5339f5ba43 (patch)
tree11922d44d5af3bcebef7a2eed26a067ac055297a /src/gallium/docs/source/screen.rst
parentfb63c43fd1b7adb5cb4f34e7616e7d564ca178e5 (diff)
gallium: introduce PIPE_CAP_MEMOBJ
This can be used to guard support for EXT_memory_object and related extensions. v2: update gallium docs v3 (Timothy Arceri): - add cap to nv50 Signed-off-by: Andres Rodriguez <[email protected]> Reviewed-by: Marek Olšák <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]>
Diffstat (limited to 'src/gallium/docs/source/screen.rst')
-rw-r--r--src/gallium/docs/source/screen.rst1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst
index 5c5c7909f0d..be14ddd0c0d 100644
--- a/src/gallium/docs/source/screen.rst
+++ b/src/gallium/docs/source/screen.rst
@@ -403,6 +403,7 @@ The integer capabilities:
``PIPE_QUERY_SO_OVERFLOW_ANY_PREDICATE`` query types are supported. Note that
for a driver that does not support multiple output streams (i.e.,
``PIPE_CAP_MAX_VERTEX_STREAMS`` is 1), both query types are identical.
+* ``PIPE_CAP_MEMOBJ``: Whether operations on memory objects are supported.
.. _pipe_capf: