diff options
| author | Nicolai Hähnle <[email protected]> | 2016-01-11 17:38:08 -0500 |
|---|---|---|
| committer | Nicolai Hähnle <[email protected]> | 2016-01-14 09:39:38 -0500 |
| commit | 654670b4048ae079879a04c41829902060a93931 (patch) | |
| tree | b9265281a70b2805571a804434f6fb75f375dc84 /src/gallium/docs | |
| parent | 6f4ae810056a1f3c53efe6f0576b9b9c4e847a80 (diff) | |
gallium: add PIPE_CAP_INVALIDATE_BUFFER
It makes sense to re-use pipe->invalidate_resource for the purpose of
glInvalidateBufferData, but this function is already implemented in vc4
where it doesn't have the expected behavior. So add a capability flag
to indicate that the driver supports the expected behavior.
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/docs')
| -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 c8f5f6a461e..81de7f85708 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -301,6 +301,8 @@ The integer capabilities: alignment for pipe_shader_buffer::buffer_offset, in bytes. Maximum value allowed is 256 (for GL conformance). 0 is only allowed if shader buffers are not supported. +* ``PIPE_CAP_INVALIDATE_BUFFER``: Whether the use of ``invalidate_resource`` + for buffers is supported. .. _pipe_capf: |