- Feb 01, 2010
-
-
Brice Goglin authored
-
Brice Goglin authored
-
Brice Goglin authored
-
- Jan 29, 2010
-
-
Jakob Bornecrantz authored
Leftover that was never used in this driver
-
Jose Fonseca authored
-
Brian Paul authored
See comments for details.
-
Brian Paul authored
-
Brian Paul authored
-
Brian Paul authored
Commit 2708ddfb caused a few regressions. We need to check/validate state after calling bind_arrays() because it might set the _NEW_ARRAYS flag if the varying VP inputs change. The symptom of this problem was some attribute arrays being ignored (or interpreted as constant-valued) in glDrawRangeElements or glMultiDrawElements. A follow-on patch will add some additional asserts to try to catch this kind of thing in the future.
-
Brian Paul authored
...rather than checking/validating before all the calls to _mesa_valid_to_render() and valid_to_render(). The next patch will actually fix some bugs...
-
- Jan 28, 2010
-
-
Jose Fonseca authored
-
Jose Fonseca authored
Otherwise geometry might end up in the wrong rendertarget.
-
Jose Fonseca authored
-
Jose Fonseca authored
-
Jose Fonseca authored
This allows for z32f depth format to work correctly.
-
Jose Fonseca authored
We'll likely support much more formats, but doing this allows to run more testsuites without immediately hit assertion failures.
-
Jose Fonseca authored
Not since 6094e79f. Drivers now need to flush draw module explicitely (which explains why all those previous commits adding draw_flushes calls were necessary). This is a good thing, but it's tricky to get this right in face of user buffers (it's not even clear who has the responsibility to flush when a user buffer is seen -- statetracker or pipe driver), so just force flush (temporarily) since it's not a bottleneck now.
-
Jose Fonseca authored
That is: - check for no op - update/flush draw module - update bound state and mark it as dirty In particular flushing the draw module is important since it may contain unflushed primitives which would otherwise be draw with wrong state.
-
Jose Fonseca authored
Otherwise geometry will end up in the wrong rendertarget.
-
Jose Fonseca authored
Cherry-picked from dec35d04.
-
-
-
Jose Fonseca authored
Now fslight looks perfect.
-
Jose Fonseca authored
-
Jose Fonseca authored
-
Jose Fonseca authored
It should be a bitcast as the integer value is actually an encoded FP already.
-
Jakob Bornecrantz authored
-
-
Jose Fonseca authored
-
Brian Paul authored
-
Brian Paul authored
These changes were originally submitted by Karl Schultz for Mesa 7.7-rc2 but weren't applied.
-
Original patch fixed up by Brian Paul.
-
- Jan 27, 2010
-
-
Alex Deucher authored
-
Alex Deucher authored
also clarify some other const values.
-
-
same variable used for 2 different temp registers fixes e.g. glsl/bump
-
Jose Fonseca authored
The driver (or preferably the hardware) should handle out of bounds indices. If there are problems then it's better to detect those in the debug builds.
-
Jose Fonseca authored
Do this by extending the nearest range to cover the new range. This fixes an access fault in Call of Duty which was doing many disjoint glBufferSubData calls.
-
Jose Fonseca authored
Actually the current XOR implementation is an INVERT. This fixes rectangle selection in Maya.
-
Keith Whitwell authored
-