From 62f44f670bb0162e89fd4786af877f8da9ff607c Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Mon, 5 Mar 2012 13:45:00 +0100 Subject: Revert "gallium: add flag PIPE_TRANSFER_MAP_PERMANENTLY" This reverts commit 0950086376b1c8b7fb89eda81ed7f2f06dee58bc. It was decided to refactor the transfer API instead of adding workarounds to address the performance issues. --- src/gallium/include/pipe/p_defines.h | 16 ---------------- 1 file changed, 16 deletions(-) (limited to 'src/gallium/include/pipe') diff --git a/src/gallium/include/pipe/p_defines.h b/src/gallium/include/pipe/p_defines.h index ff6c07dddd0..889fc9961f4 100644 --- a/src/gallium/include/pipe/p_defines.h +++ b/src/gallium/include/pipe/p_defines.h @@ -225,22 +225,6 @@ enum pipe_transfer_usage { */ PIPE_TRANSFER_MAP_DIRECTLY = (1 << 2), - /** - * The transfer should map the resource storage directly and the GPU should - * be able to see what the CPU has written. Such a storage may stay mapped - * while issuing draw commands which use it. The only allowed usage is - * non-overlapping writes which are suballocated out of a big buffer. - * The minimum allowed alignment of suballocations is 256 bytes (this is - * a subject to change). - * The flag is intended to be used to avoid mapping and unmapping - * resources repeatedly when doing uploads and draws intermixed. - * - * The driver may return NULL if that isn't possible, and the state - * tracker needs to cope with that and use an alternative path - * without this flag. - */ - PIPE_TRANSFER_MAP_PERMANENTLY = (1 << 3), - /** * Discards the memory within the mapped region. * -- cgit v1.2.3