History log of /external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
66d45567b4e2c6f2585789b68667e6c00b7567e1 04-Dec-2010 Marek Olšák <maraeo@gmail.com> r300g: optimize looping over atoms

This also removes DBG_STATS (the stats can be obtained with valgrind instead).
/external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c
a57f84251926045a3358822d0fd92ca95a4f0fde 16-Jul-2010 Chia-I Wu <olv@lunarg.com> gallium: Keep only pipe_context::draw_vbo.

That is, remove pipe_context::draw_arrays, pipe_context::draw_elements,
pipe_context::draw_arrays_instanced,
pipe_context::draw_elements_instanced,
pipe_context::draw_range_elements.
/external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c
6d28bf917fb1d741d90fd3f05c22769376021fca 15-Jul-2010 Chia-I Wu <olv@lunarg.com> gallium: Implement draw_vbo and set_index_buffer for all drivers.

Some drivers define a generic function that is called by all drawing
functions. To implement draw_vbo for such drivers, either draw_vbo
calls the generic function or the prototype of the generic function is
changed to match draw_vbo.

Other drivers have no such generic function. draw_vbo is implemented by
calling either draw_arrays and draw_elements.

For most drivers, set_index_buffer does not mark the state dirty for
tracking. Instead, the index buffer state is emitted whenever draw_vbo
is called, just like the case with draw_elements. It surely can be
improved.
/external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c
0a9510814e2dfff57f7d73cc68aece0554ad794d 25-Jun-2010 Marek Olšák <maraeo@gmail.com> r300g: turn rasterizer state into a command buffer
/external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c
cb17f5ee752d07d82e9b079c6bda9d89e51c7108 12-Jun-2010 Marek Olšák <maraeo@gmail.com> r300g: move two-sided stencilref fallback to its own file
/external/mesa3d/src/gallium/drivers/r300/r300_render_stencilref.c