From 654670b4048ae079879a04c41829902060a93931 Mon Sep 17 00:00:00 2001 From: Nicolai Hähnle Date: Mon, 11 Jan 2016 17:38:08 -0500 Subject: gallium: add PIPE_CAP_INVALIDATE_BUFFER MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- src/gallium/docs/source/screen.rst | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/gallium/docs/source') 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: -- cgit v1.2.3