| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The boolean that the server gives us for whether the region is tiled was
getting used as the enum for what tiling mode. Instead, guess the correct
tiling in screen setup.
Also, fix the Y-tiling pitch setup. The pitch to the next tile in Y is
32 scanlines, not 8.
|
| | |
| | |
| | |
| | |
| | |
| | | |
It turns out that it's not just deviceID dependent, and there's some additional
undefined factor that determines the bit 6 swizzling. It's now controllable
with swizzle_mode=[012] until we get a response on how to automatically detect.
|
| | |
| | |
| | |
| | |
| | | |
This was broken in the merge of 965 blit support. It tried to lock only
when things were already locked.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Most of these were to ensure that caches got synchronized between 2d (or meta)
rendering and later use of the target as a source, such as for texture
miptree setup. Those are replaced with intel_batchbuffer_emit_mi_flush(),
which just drops an MI_FLUSH. Most of the remainder were to ensure that
REFERENCES_CLIPRECTS batchbuffers got flushed before the lock was dropped.
Those are now replaced by automatically flushing those when dropping the lock.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
This lets GEM use pwrite, for an additional 4% or so speedup.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The fencing code is not required, and waiting on the fences defeated one of
the purposes of the extension, which is to allow asynchronous readpixels.
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The no_rast fallback was getting partially overwritten by later TNL init,
resulting in a segfault when things were in a mixed-up state.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Apparently a bit gets flipped in the addressing for some rows of each tile.
|
| | | | |
| | | | |
| | | | |
| | | | | |
This is an API breakage only.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The objects are swappable, so we're less concerned by excessive object
allocation now, and it's about a 20% performance improvement. If we get
concerns about the memory consumption from others, we can look into a
compromise position later.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Swap buffers is a fairly reasonable time to wait for the hardware for a
while; this keeps us from overrunning the ring.
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
src/mesa/drivers/dri/common/dri_bufmgr.h
src/mesa/drivers/dri/intel/intel_bufmgr_ttm.c
src/mesa/drivers/dri/intel/intel_bufmgr_ttm.h
src/mesa/drivers/dri/intel/intel_ioctl.c
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is good for about 5% on ipers on 965, and should help any cpu-bound app.
|