Marek Olšák e73bf3b805 gallium: add start_slot parameter to set_vertex_buffers ... This allows updating only a subrange of buffer bindings. set_vertex_buffers(pipe, start_slot, count, NULL) unbinds buffers in that range. Binding NULL resources unbinds buffers too (both buffer and user_buffer must be NULL). The meta ops are adapted to only save, change, and restore the single slot they use. The cso_context can save and restore only one vertex buffer slot. The clients can query which one it is using cso_get_aux_vertex_buffer_slot. It's currently set to 0. (the Draw module breaks if it's set to non-zero) It should decrease the CPU overhead when using a lot of meta ops, but the drivers must be able to treat each vertex buffer slot as a separate state (only r600g does so at the moment). I can imagine this also being useful for optimizing some OpenGL use cases. Reviewed-by: Brian Paul <brianp@vmware.com>		2012-10-31 00:55:13 +01:00
..
graw	gallium: add start_slot parameter to set_vertex_buffers	2012-10-31 00:55:13 +01:00
python/tests/regress/fragment-shader	Add a test for the compare opcode.	2012-02-23 12:29:29 +00:00
trivial	gallium: unify transfer functions	2012-10-11 21:12:16 +02:00
unit	tests: Use printf instead of debug_printf in u_format_compatible_test.	2012-10-25 23:09:59 -07:00