linux/drivers/gpu, branch v2.6.28

drm/radeon: fix correctness of irq_enabled check for radeon.

2008-12-23T00:50:12Z

This check was introduced with the logic the wrong way around. Fixes regression: http://bugzilla.kernel.org/show_bug.cgi?id=12216 Tested-by: François Valenduc Signed-off-by: Dave Airlie

drm/i915: GEM on PAE has problems - disable it for now.

2008-12-19T05:38:34Z

On PAE systems, GEM allocates pages using shmem, and passes these pages to be bound into AGP, however the AGP interfaces + the x86 set_memory interfaces all take unsigned long not dma_addr_t. The initial fix for this was a mess, so we need to do this correctly for 2.6.29. Signed-off-by: Dave Airlie

drm/i915: Don't return busy for buffers left on the flushing list.

2008-12-19T05:34:32Z

These buffers don't have active rendering still occurring to them, they just need either a flush to be emitted or a retire_requests to occur so that we notice they're done. Return unbusy so that one of the two occurs. The two expected consumers of this interface (OpenGL and libdrm_intel BO cache) both want this behavior. Signed-off-by: Eric Anholt Acked-by: Keith Packard Signed-off-by: Dave Airlie

drm/i915: Disable the GM965 MSI errata workaround.

2008-12-09T05:37:24Z

Since applying the fix suggested by the errata (disabling MSI), we've had issues with interrupts being stuck on despite IIR being 0 on GM965 hardware. Most reporters of the issue have confirmed that turning MSI back on fixes things, and given the difficulties experienced in getting reliable MSI working on Linux, it's believable that the errata was about software issues and not actual hardware issues. Signed-off-by: Dave Airlie

drm/i915: Don't return error in evict_everything when we get to the end.

2008-12-09T05:37:17Z

Returning -ENOMEM errored all the way out of execbuf, so the rendering never occurred. Signed-off-by: Dave Airlie

drm/radeon: don't actually enable the IRQ regs until irq is enabled

2008-12-09T05:30:50Z

vblank can try and enable the IRQ registers before we've set the interrupt handler up. Signed-off-by: Dave Airlie

drm/i915: Return error in i915_gem_set_to_gtt_domain if we're not in the GTT.

2008-12-04T01:24:47Z

It's only for flushing caches appropriately for GTT access, not for actually getting it there. Prevents potential smashing of cpu read/write domains on unbound objects. Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie

drm/i915: Retry execbuffer pinning after clearing the GTT

2008-12-04T01:22:06Z

If we fail to pin all of the buffers in an execbuffer request, go through and clear the GTT and try again to see if its just a matter of fragmentation Signed-off-by: Keith Packard Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie

drm/i915: Move the execbuffer domain computations together

2008-12-04T01:22:02Z

This eliminates the dev_set_domain function and just in-lines it where its used, with the goal of moving the manipulation and use of invalidate_domains and flush_domains closer together. This also avoids calling add_request unless some domain has been flushed. Signed-off-by: Keith Packard Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie

drm/i915: Rename object_set_domain to object_set_to_gpu_domain

2008-12-04T01:21:58Z

Now that the CPU and GTT domain operations are isolated to their own functions, the previously general-purpose set_domain function is now used only to set GPU domains. It also has no failure cases, which is important as this eliminates any possible interruption of the computation of new object domains and subsequent emmission of the flushing instructions into the ring. Signed-off-by: Keith Packard Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie