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

Age	Commit message (Collapse)	Author
2011-01-07	mesa: Directly include mfeatures.h in files that perform feature tests.	Vinson Lee

2010-10-14	Drop the "neutral" tnl module	Kristian Høgsberg
	Just always check for FLUSH_UPDATE_CURRENT and call Driver.BeginVertices when necessary. By using the unlikely() macros, this ends up as a 10% performance improvement (for isosurf, anyway) over the old, complicated function pointer swapping.
2010-10-13	Drop GLcontext typedef and use struct gl_context instead	Kristian Høgsberg

2010-07-31	mesa: Include missing headers in vtxfmt.h.	Vinson Lee
	Include compiler.h for INLINE symbol. Include mtypes.h for GLcontext symbol.
2009-09-30	mesa/main: New feature FEATURE_beginend.	Chia-I Wu
	This feature corresponds to the Begin/End paradigm. Disabling this feature also eliminates the use of GLvertexformat completely.
2004-02-24	added some const keywords	Brian Paul

2003-07-17	Merge Jose's documentation and core Mesa changes from embedded branch	Keith Whitwell

2003-06-05	Removed all RCS / CVS tags (Id, Header, Date, etc.) from everything.	Ian Romanick

2002-10-29	updated email addresses	Brian Paul

2001-03-12	Consistent copyright info (version number, date) across all files.	Gareth Hughes

2001-03-11	Clean up install, restore for exec vtxfmts.	Gareth Hughes

2001-03-11	Support for swappable tnl modules.	Gareth Hughes
	Core Mesa provides a neutral tnl module that verifies the currently module before installing the tnl function pointers in a lazy fashion. It also records which tnl functions have been swapped out, and only restores these when tnl modules themselves are swapped. Fallback strategies: Drivers set a bitmask of dangerous stage changes. When such a state change occurs, the driver should restore the neutral tnl module via _mesa_restore_exec_vtxfmt(). The neutral tnl module will call _mesa_update_state(), followed by ctx->Driver.ValidateTnlModule() if the validation bitmask matches the new state bitmask. The driver should call _tnl_wakeup_exec() if it can no longer handle the current state, which will revert to the default tnl module. In this case, previous vertices should be replayed as required (depending on the current primitive) after the new tnl module is installed. If the driver uses chooser functions for any part of the tnl module, these should generally be reinstalled as part of the fallback to the neutral tnl module. For example, if the lighting state changes, a driver might fall back to the neutral tnl module, verify that the current lighting state can be handled, and use the chooser function to pick the most efficient implementation of the current lighting state. It is up to the drivers to detect and handle fallback cases caused by tnl function calls themselves (such as glTexCoord4f* if the current tnl module can't handle projected textures, for example).
2000-11-24	New files...	Keith Whitwell