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

Age	Commit message (Collapse)	Author
2008-04-03	draw: add passthrough path to the pipeline	Keith Whitwell
	This handles the case where bypass_vs is set, but vertices need to go through the pipeline for some reason - eg unfilled polygon mode. Demonstrates how to drive the pipeline from inside one of these things.
2008-04-02	draw: add missing break statement	Keith Whitwell

2008-04-02	draw: Set the backend prim in the pt 'prepare' operation	Keith Whitwell
	Leaving it until 'run' is bad as the primitive is pretty much state for some drivers and so needs to get set early. In some drivers this is used to determine things like vertex format, etc -- by the time we get to 'run', it's too late to change this.
2008-03-27	gallium: replace PIPE_ATTRIB_MAX with PIPE_MAX_ATTRIBS	Brian
	The later follows the naming scheme of other limits. Keep the old definition until all possible usage is updated.
2008-03-23	draw: rename emit functions to match pipe_format names	Keith Whitwell

2008-03-23	draw: restructure fetch/emit as a pair of function calls	Keith Whitwell

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.