diff options
| author | Marek Olšák <[email protected]> | 2013-02-26 17:20:25 +0100 |
|---|---|---|
| committer | Marek Olšák <[email protected]> | 2013-03-01 13:46:32 +0100 |
| commit | 6f25de6711491bbcfc906cd8804f30acc6534b2d (patch) | |
| tree | 134c428c9c15525f01187ebdffb5ee51d572587d /src/gallium/drivers/r600/r600.h | |
| parent | 9dd18f43a4db73be73dfbf2e9950ae4dfaf6322e (diff) | |
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 <[email protected]>
Diffstat (limited to 'src/gallium/drivers/r600/r600.h')
| -rw-r--r-- | src/gallium/drivers/r600/r600.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/gallium/drivers/r600/r600.h b/src/gallium/drivers/r600/r600.h index 11dbb3bad37..dfd18b81a92 100644 --- a/src/gallium/drivers/r600/r600.h +++ b/src/gallium/drivers/r600/r600.h @@ -168,8 +168,6 @@ void r600_context_emit_fence(struct r600_context *ctx, struct r600_resource *fen unsigned offset, unsigned value); void r600_flush_emit(struct r600_context *ctx); -void r600_context_streamout_begin(struct r600_context *ctx); -void r600_context_streamout_end(struct r600_context *ctx); void r600_need_cs_space(struct r600_context *ctx, unsigned num_dw, boolean count_draw_in); void r600_need_dma_space(struct r600_context *ctx, unsigned num_dw); void r600_dma_copy(struct r600_context *rctx, |