From 1eedebc65b02130ef7a27062a1ed67972a317a08 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Marek=20Ol=C5=A1=C3=A1k?= Date: Thu, 1 Nov 2012 02:00:37 +0100 Subject: [PATCH] r600g: re-enable handling of DISCARD_RANGE, improving performance It seems to work for me now. Even the graphics corruption is gone. This also boosts performance in Reaction Quake. --- src/gallium/drivers/r600/r600_buffer.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/gallium/drivers/r600/r600_buffer.c b/src/gallium/drivers/r600/r600_buffer.c index 116ab51196f..968824ea1bb 100644 --- a/src/gallium/drivers/r600/r600_buffer.c +++ b/src/gallium/drivers/r600/r600_buffer.c @@ -136,7 +136,6 @@ static void *r600_buffer_transfer_map(struct pipe_context *ctx, r600_set_constants_dirty_if_bound(rctx, rbuffer); } } -#if 0 /* this is broken (see Bug 53130) */ else if ((usage & PIPE_TRANSFER_DISCARD_RANGE) && !(usage & PIPE_TRANSFER_UNSYNCHRONIZED) && rctx->screen->has_streamout && @@ -159,7 +158,6 @@ static void *r600_buffer_transfer_map(struct pipe_context *ctx, ptransfer, data, staging); } } -#endif data = rctx->ws->buffer_map(rbuffer->cs_buf, rctx->cs, usage); if (!data) { -- 2.30.2