From 6f25de6711491bbcfc906cd8804f30acc6534b2d Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Tue, 26 Feb 2013 17:20:25 +0100 Subject: r600g: atomize streamout enabling This doesn't fix any issue we know of, but there indeed is a week spot in draw_vbo where streamout can fail. After streamout is enabled, the need_cs_space call can flush the context, which causes the streamout to be disabled right after it was enabled and bad things happen. One way to fix it is to atomize the beginning part, so that no context flush can happen between streamout enabling and the first drawing. Tested-by: Andreas Boll --- src/gallium/drivers/r600/evergreen_compute.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'src/gallium/drivers/r600/evergreen_compute.c') diff --git a/src/gallium/drivers/r600/evergreen_compute.c b/src/gallium/drivers/r600/evergreen_compute.c index 128464e101a..8b3104e40a1 100644 --- a/src/gallium/drivers/r600/evergreen_compute.c +++ b/src/gallium/drivers/r600/evergreen_compute.c @@ -438,10 +438,6 @@ static void compute_emit_cs(struct r600_context *ctx, const uint *block_layout, ctx->ws->buffer_wait(onebo->buf, 0); COMPUTE_DBG("...\n"); - - ctx->streamout_start = TRUE; - ctx->streamout_append_bitmask = ~0; - } -- cgit v1.2.3