| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically, the application enables client vertex and color arrays,
renders something, then disables color array, and renders something
else (using vertex array only). Even though the color array is
disabled (and the pointer is no longer valid), the driver still tries
to read color data from this array (which results in an exception).
This is because enabling/disabling array does not trigger
_ae_update_state() and the list of enabled arrays is not updated.
_ae_update_state() it's called on the first state validation only (as
all the "dirty" flags are set at the beginning). Any further change to
client arrays' state has no effect.
|
|
|
|
| |
Patch is correctly applied this time.
|
| |
|
|
|
|
|
|
|
|
| |
Otherwise, we would ping-pong objects to GTT and back as we did pwrite on
indices (flushed and mapped to GTT) and mapped for vertices (moved back to
CPU domain).
Fixes bug #17180.
|
|
|
|
| |
Caught by texturing/gen-teximage test in piglit.
|
|
|
|
|
|
|
|
|
| |
If we copy the area before reporting the damage in this area, the server may
restore buffered data over the new data, leading to artefacts on the screen.
Reproducable with two cursors (second of which is SW rendered) and moving
windows around in compiz.
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=16384 .
|
|
|
|
|
|
|
|
|
| |
Previously, the updated images would be ignored because the miptree in the
image matched the miptree in the object, even though Mesa core had just attached
updated contents in ->Data. Additionally, Mesa core could have tried to
free inside our miptree if it had already been validated.
Fixes bug #17077.
|
| |
|
|
|
|
|
| |
(cherry picked from commit 9bc9e0ecb0fb2069b2c123e665eb2118e358098f which
was lost in a merge)
|
|
|
|
|
|
|
| |
should fix fd.o 14441
(cherry-picked from commit d4244683a61f66cfb78408a37cf2587587847f96 which was
lost in a merge)
|
|
|
|
| |
(bug #16852, #16853)
|
|
|
|
|
| |
Is there some kind of git hook we could use to keep me from committing
after like 10PM or so?
|
| |
|
|
|
|
|
| |
This uses fog HW instead of fragment programs.
If it breaks you, let me know!
|
| |
|
|
|
|
|
|
| |
17173
Also, move GL_TEXTURE_RECTANGLE init code into separate function.
|
|
|
|
| |
Signed-off-by: Corbin Simpson <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes progs/glsl/points.c
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Accessing a GLboolean via an int pointer on big-endian == bad.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/mesa/drivers/dri/intel/intel_span.c
src/mesa/main/fbobject.c
This converts the i915 driver to use the GEM interfaces for object management.
|
| |
| |
| |
| |
| |
| | |
To do this, I had to clean up some of 965 state upload stuff. We may end
up over-emitting state in the aperture overflow case, but that should be rare,
and I'd rather have the simplification of state management.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Fixes oglconform rbGetterFuncs testcase. The span code for this mode hasn't
actually been tested.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/mesa/drivers/dri/common/dri_bufmgr.c
src/mesa/drivers/dri/i965/brw_wm_surface_state.c
|
| | |
| | |
| | |
| | | |
Fixes some oglconform fbo testcases.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, we would just store the data as malloced memory hanging off the
object, which would get memcpyed in at validate time. This broke an
oglconform render-to-texture test, since validate wasn't called but a miptree
was expected.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This will avoid clflushing entire buffers for small acesses, such as those
commonly used by regression tests.
|
| | | |
|
| | |
| | |
| | |
| | | |
Didn't hurt 915, but needed for 965.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This lets us avoid duplicated code for doing so, including the depthstencil
paths that aren't covered by SpanRenderStart/Finish. Those paths were
missing the span funcs setup, leading to a null dereference in the fbotexture
demo.
|
| | |
| | |
| | |
| | |
| | | |
Bump the driver date and insert the string "GEM". When running tests,
this make it much easier to know that the right driver is being used.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Those functions rely on being able to treat the GET_PTR returned value as an
array indexed by x, but that's not the case for our tiling.
Bug #16387
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
The dri_bo_map()s that follow will take care of idling the hardware as needed.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have something similar in the X Server that covers X Server rendering, this
is the equivalent here for rendering to the front buffer. If we cared about
avoiding this at glFlush time, we could only do this when some actual
frontbuffer rendering had occurred.
Bug #16392.
|
| | |
| | |
| | |
| | |
| | | |
Apparently in Y mode we get bit 6 ^ bit 9. The reflect demo in 'd' mode now
displays correctly.
|