summaryrefslogtreecommitdiff
path: root/src/gallium/auxiliary/cso_cache/cso_context.h
AgeCommit message (Collapse)Author
2008-04-24gallium: make cso_release_all() publicBrian Paul
2008-04-24gallium: added cso_delete_vertex_fragment_shader() functionsBrian Paul
The state tracker now uses these functions to free shaders, rather than the pipe->delete_vs/fs-state() functions. Before, we could get in a situation where we free() a shader and happen to alloc() a new one at the same address. The cso_set_vertex/fragment_shader() function would no-op the state change since the pointers were the same. This led to problems elsewhere, of course. The new delete functions null-out the CSO's current shader pointers.
2008-04-21make the api consistent (all set functions return pipe_error status)Zack Rusin
2008-04-21initial stab at error handling in csoZack Rusin
2008-04-21cso: provide functions to bind fs/vs handles directlyKeith Whitwell
2008-03-19gallium: implement CSO save/restore functions for use by meta operations ↵Brian
(blit, gen-mipmaps, quad-clear, etc) Also, additional cso_set_*() functions for viewport, framebuffer, blend color, etc. state.
2008-03-18gallium: added cso_unset_*() functionsBrian
If we go behind the CSO context's back and set pipe state directly we need to invalidate the CSO's 'current' pointers. This will be revisited...
2008-03-09cso: add a higher-level interface which does all pipe interactions to set a ↵Keith Whitwell
given state