summaryrefslogtreecommitdiff
path: root/src/gallium/include
diff options
context:
space:
mode:
authorRoland Scheidegger <sroland@vmware.com>2010-05-17 21:02:24 +0200
committerRoland Scheidegger <sroland@vmware.com>2010-05-17 21:02:24 +0200
commit379db6a36b32912be8fd8808ceb95ca5cffa7850 (patch)
tree8003d4f99ba73813c33607abec997d1a0a8c8577 /src/gallium/include
parent6272d7632a8d2948e45698d1c75eae8c441c3916 (diff)
gallium: clean up resource_copy_region function
Previously, surface_copy was said to allow overlapping blits, and it was "optional". However, some state trackers actually assumed it is always present, and quite some code (like in u_blit) assumed overlapping isn't allowed. Hence, resource_copy_region (and in the same spirit, resource_fill_region) is now mandatory, but overlapping blits are no longer allowed. A driver can plug in the cpu fallback util_resource_copy_region if it does not want to provide its own implementation, though this is not optimal.
Diffstat (limited to 'src/gallium/include')
-rw-r--r--src/gallium/include/pipe/p_context.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/gallium/include/pipe/p_context.h b/src/gallium/include/pipe/p_context.h
index 6ce8ba953a..6b72983176 100644
--- a/src/gallium/include/pipe/p_context.h
+++ b/src/gallium/include/pipe/p_context.h
@@ -238,8 +238,6 @@ struct pipe_context {
/**
* Resource functions for blit-like functionality
*
- * The pipe driver is allowed to set these functions to NULL, and in that
- * case, they will not be available.
* If a driver supports multisampling, resource_resolve must be available.
*/
/*@{*/