On Sat, 2009-03-21 at 18:02 -0700, Dave Airlie wrote:
Hi all,
So I had to drop texture tiling when I did the radeon-rewrite but I'd like
to bring them back.
Now with traditional drivers, we have the mesa copy of the texture and the
card copy, and we usually texture from VRAM only, so we
On Sat, 2009-03-21 at 18:02 -0700, Dave Airlie wrote:
Hi all,
So I had to drop texture tiling when I did the radeon-rewrite but I'd like
to bring them back.
Now with traditional drivers, we have the mesa copy of the texture and the
card copy, and we usually texture from VRAM only, so we
On Sun, 2009-03-22 at 01:02 +, Dave Airlie wrote:
I'm just wondering if anyone has already tackled this in any driver, and
how this could work best. Does Gallium provide surface accessors for
textures like spans?
The intel driver de-tiles in the software span accessing functions. Or
is
textures like spans?
The intel driver de-tiles in the software span accessing functions. Or
is there something I'm missing here? Do textures go through some other
path?
It detiles buffer access via spans, textures don't go via spans from what
I can see, the texstore code seems to
On Sat, Mar 21, 2009 at 9:02 PM, Dave Airlie airl...@linux.ie wrote:
I'm just wondering if anyone has already tackled this in any driver, and
how this could work best. Does Gallium provide surface accessors for
textures like spans?
I'm sort of thinking I keep two buffers objects, one sw only
Hi all,
So I had to drop texture tiling when I did the radeon-rewrite but I'd like
to bring them back.
Now with traditional drivers, we have the mesa copy of the texture and the
card copy, and we usually texture from VRAM only, so we can upload to VRAM
and tile on the way, and if we hit a sw
On 3/21/09, Dave Airlie airl...@linux.ie wrote:
Hi all,
So I had to drop texture tiling when I did the radeon-rewrite but I'd like
to bring them back.
Now with traditional drivers, we have the mesa copy of the texture and the
card copy, and we usually texture from VRAM only, so we can
