i915g: rip out ->sw_tiled
authorDaniel Vetter <daniel.vetter@ffwll.ch>
Fri, 19 Nov 2010 22:38:18 +0000 (23:38 +0100)
committerJakob Bornecrantz <wallbraker@gmail.com>
Sun, 21 Nov 2010 15:41:18 +0000 (16:41 +0100)
commitf77a2690b463aa36297aec2a5035a9de68268dd9
tree79db816944c35315e45b3e8f45f5b40960a3b441
parentbf10055cffcc5d62a3e214674846185bfaf253e7
i915g: rip out ->sw_tiled

It looks like this was meant to facilitate unfenced access to textures/
color/renderbuffers. It's totally incomplete and fundamentally broken
on a few levels:
- broken: The kernel needs to about every tiled bo to fix up bit17
  swizzling on swap-in.
- unflexible: fenced/unfenced relocs from execbuffer2 do the same, much
  simpler.
- unneeded: with relaxed fencing tiled gem bos are as memory-efficient
  as this trick.

Hence kill it.

Reviewed-by: Jakob Bornecrantz <wallbraker@gmail.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Jakob Bornecrantz <wallbraker@gmail.com>
src/gallium/drivers/i915/i915_resource.h
src/gallium/drivers/i915/i915_resource_texture.c
src/gallium/drivers/i915/i915_state_emit.c
src/gallium/drivers/i915/i915_state_sampler.c