android-x86-mesa.git - Androïd/x86 port of Mesa drivers

Age	Commit message (Collapse)	Author
2009-06-18	draw: Replace pointer arithmetic with cast.	José Fonseca
	Using uintptr_t as intermediate type for pointer -> integer conversions is easier to understand and does not cause any size mismatch warnings. uintptr_t is part of C99, and we already provide a suitable replacement definition for all platforms we care about.
2008-05-28	gallium: Windows CE portability fixes.	José Fonseca

2008-04-19	draw: move incoming vertex state into draw->pt	Keith Whitwell
	This state is effectively private to the vertex processing part of the draw module.
2008-03-24	Revert "draw: Fix #include order to fix Linux build."	Keith Whitwell
	This reverts commit a6d17bf671d6bfbb187a62ba14b9ad08fb5dafe1.
2008-03-24	draw: Fix #include order to fix Linux build.	Michel Dänzer

2008-03-23	draw: fix crlf	Keith Whitwell

2008-03-23	draw: fix some unsigned vs ushort confusion	Keith Whitwell
	Middle-end elements are ushort, but prior to that have to treat all elements as unsigned to avoid wrapping and/or overruns.
2008-03-23	gallium: beginnings of draw module vertex rework	Keith Whitwell
	Trying to put a structure in place that we can actually optimize. Initially just implementing a passthrough mode, this will fairly soon replace all the vertex_cache/prim_queue/shader_queue stuff that's so hard to understand... Split the vertex processing into a couple of distinct stages: - Frontend - Prepares two lists of elements (fetch and draw) to be processed by the next stage. This stage doesn't fetch or draw vertices, but makes the decision which to draw. Multiple implementations of this will implement different strategies, currently just a vcache implementation. - MiddleEnd - Takes the list of fetch elements, fetches them, runs the vertex shader, cliptest, viewport transform on them to produce a linear array of vertex_header vertices. - Passes that list of vertices, plus the draw_elements (which index into that list) onto the backend - Backend - Either the existing primitive/clipping pipeline, or the vbuf_render hardware backend provided by the driver. Currently, the middle-end is the old passthrough code, and it build hardware vertices, not vertex_header vertices as above. It may be that passthrough is a special case in this respect.