Mesa - My Mesa repository

Age	Commit message (Collapse)	Author
2010-02-10	r300g: Work around "defect" in r300compiler.	Corbin Simpson
	r300compiler doesn't handle half swizzles for vert shaders, which don't have them. So, for now, disable them.
2010-02-09	r300g: Fix off-by-one errors in array bounds assertions.	Vinson Lee

2010-02-02	r300compiler, r300 classic, r300g: Add support for MRTs in the frag shader.	Corbin Simpson
	This maybe breaks the vert compiler. Hopefully not.
2010-01-06	r300g: add WPOS	Marek Olšák

2009-12-19	r300g: add texture compare modes	Marek Olšák

2009-12-01	r300g: simplify allocations of FS input registers	Marek Olšák

2009-12-01	r300g: clean up derived states	Marek Olšák
	The state setups which aren't derived anymore have been moved to the VS and FS objects.
2009-10-21	r300g: Cleanup old static shader state.	Corbin Simpson

2009-10-21	r300g: Cleanup header includes.	Corbin Simpson

2009-10-03	r300g: Do not abort on fragment program compiler error	Nicolai Hähnle
	Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
2009-09-06	r300g: Debug flags infrastructure	Nicolai Hähnle
	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
2009-08-11	r300g: a typo of debug message	Cooper Yuan

2009-07-30	r300g: Use radeon compiler for fragment programs	Nicolai Hähnle
	This is entirely untested on R500, and needs more testing on R300.
2009-07-23	r300g: Actually mark shaders as translated/untranslated.	Corbin Simpson
	Also trust that Gallium will not give us TGSI that miscounts shader consts. This creates a 20x speedup on glxgears, from 8 FPS to 160 FPS.
2009-07-22	gallium: simplify tgsi_full_immediate struct	Keith Whitwell
	Remove the need to have a pointer in this struct by just including the immediate data inline. Having a pointer in the struct introduces complications like needing to alloc/free the data pointed to, uncertainty about who owns the data, etc. There doesn't seem to be a need for it, and it is unlikely to make much difference plus or minus to performance. Added some asserts as we now will trip up on immediates with more than four elements. There were actually already quite a few such asserts, but the >4 case could be used in the future to specify indexable immediate ranges, such as lookup tables.
2009-06-26	r300-gallium: organize fragment/vertex shaders	Joakim Sindholt
	Appart from separating r3xx/r5xx fragment shaders, a more consistent naming scheme has been applied. From now on: r300 = all chips r3xx = R300/R400 only r5xx = R500 only This way r300_fragment_shader is the master struct, and the structs r3xx_fragment_shader and r5xx_fragment_shader inherits it.