diff options
author | Ilia Mirkin <[email protected]> | 2015-11-09 13:27:07 -0500 |
---|---|---|
committer | Ilia Mirkin <[email protected]> | 2015-11-11 19:20:41 -0500 |
commit | 3695b253f908b58290d69e2d770209abf0c6beee (patch) | |
tree | ae49b3e0876518773e1765513a1a0f3e8245a040 /src/gallium/docs/source/context.rst | |
parent | 725fcdfbb11ff4c4399d58e08403e4e0064a8c5e (diff) |
gallium: add PIPE_CAP_CLEAR_TEXTURE and clear_texture prototype
Signed-off-by: Ilia Mirkin <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/docs/source/context.rst')
-rw-r--r-- | src/gallium/docs/source/context.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/gallium/docs/source/context.rst b/src/gallium/docs/source/context.rst index dbc087700b5..9a32716f921 100644 --- a/src/gallium/docs/source/context.rst +++ b/src/gallium/docs/source/context.rst @@ -227,6 +227,10 @@ is is also possible to only clear one or the other part). While it is only possible to clear one surface at a time (which can include several layers), this surface need not be bound to the framebuffer. +``clear_texture`` clears a non-PIPE_BUFFER resource's specified level +and bounding box with a clear value provided in that resource's native +format. + ``clear_buffer`` clears a PIPE_BUFFER resource with the specified clear value (which may be multiple bytes in length). Logically this is a memset with a multi-byte element value starting at offset bytes from resource start, going |