nv30: avoid doing extra work on clear and hitting unexpected states
Clearing can happen at a time when various state objects are incoherent and not ready for a draw. Some of the validation functions don't handle this well, so only flush the framebuffer state. This has the advantage of also not doing extra work. This works around some crashes that can happen when clearing. Signed-off-by:Ilia Mirkin <imirkin@alum.mit.edu> Reviewed-by:
Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Showing
- src/gallium/drivers/nouveau/nv30/nv30_clear.c 1 addition, 1 deletionsrc/gallium/drivers/nouveau/nv30/nv30_clear.c
- src/gallium/drivers/nouveau/nv30/nv30_context.h 1 addition, 1 deletionsrc/gallium/drivers/nouveau/nv30/nv30_context.h
- src/gallium/drivers/nouveau/nv30/nv30_draw.c 2 additions, 2 deletionssrc/gallium/drivers/nouveau/nv30/nv30_draw.c
- src/gallium/drivers/nouveau/nv30/nv30_state_validate.c 6 additions, 4 deletionssrc/gallium/drivers/nouveau/nv30/nv30_state_validate.c
- src/gallium/drivers/nouveau/nv30/nv30_vbo.c 1 addition, 1 deletionsrc/gallium/drivers/nouveau/nv30/nv30_vbo.c
Loading
Please register or sign in to comment