I'm just looking through the docs this evening and I noticed the
TXOFFSET_0 register has endian swapping for textures in hardware,

This allowed me to remove some swizzling in my own application along with
client side texturing... (i.e. more speed less processing..)

I'm thinking about how these could be used in Mesa drivers? would I be
correct in thinking the fallbacks would mess up as the Mesa copy of the
texture wouldn't be the same as what the card would be using?

I would be tempted to add a third field to the txtable for the offset and
set it up depending on the Mesa texture format...

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to