r300g: Debug flags infrastructure
authorNicolai Hähnle <nhaehnle@gmail.com>
Sun, 6 Sep 2009 13:03:51 +0000 (15:03 +0200)
committerNicolai Hähnle <nhaehnle@gmail.com>
Sun, 6 Sep 2009 13:03:52 +0000 (15:03 +0200)
commit4b01e6f614052e48971f2b2ff474fb66afc4f752
tree9fdfeb05baf7cbbe603e333182f582b5276185fd
parent9778731732b4753e79a1b786c65325a52392411d
r300g: Debug flags infrastructure

So that debugging is no longer a full-spam-or-nothing approach, you are now
supposed to set the RADEON_DEBUG environment flag just like for classic Mesa.

The available debug flags are different, however. Just running an OpenGL
application with RADEON_DEBUG set to an arbitrary string will print out
helpful information.

Everything must be compiled with -DDEBUG for any of this to work
src/gallium/drivers/r300/Makefile
src/gallium/drivers/r300/r300_context.c
src/gallium/drivers/r300/r300_context.h
src/gallium/drivers/r300/r300_cs.h
src/gallium/drivers/r300/r300_debug.c [new file with mode: 0644]
src/gallium/drivers/r300/r300_emit.c
src/gallium/drivers/r300/r300_fs.c
src/gallium/drivers/r300/r300_render.c
src/gallium/drivers/r300/r300_state_derived.c
src/gallium/drivers/r300/r300_vs.c