diff options
author | Marek Olšák <[email protected]> | 2018-01-27 01:52:08 +0100 |
---|---|---|
committer | Marek Olšák <[email protected]> | 2018-02-17 04:20:55 +0100 |
commit | 8e7222f4e5d624313bf972637d22b49fc7200383 (patch) | |
tree | 5c83d524eefcd1384d4636505a9e4782bd1dee65 /src/gallium/docs | |
parent | 834d221512fae8dd290d347fec071c4adbe140ed (diff) |
gallium: allow drivers to impose BO flags restrictions on constant buffer 0
Required by radeonsi for optimal behavior.
Diffstat (limited to 'src/gallium/docs')
-rw-r--r-- | src/gallium/docs/source/screen.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index 95b62534493..e375d67a4b6 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -414,6 +414,10 @@ The integer capabilities: contexts can return 0. * ``PIPE_CAP_FENCE_SIGNAL``: True if the driver supports signaling semaphores using fence_server_signal(). +* ``PIPE_CAP_CONSTBUF0_FLAGS``: The bits of pipe_resource::flags that must be + set when binding that buffer as constant buffer 0. If the buffer doesn't have + those bits set, pipe_context::set_constant_buffer(.., 0, ..) is ignored + by the driver, and the driver can throw assertion failures. .. _pipe_capf: |