Re: Mesa bug in new teximage code

[Brian P. <bri...@tu...>]

John, I'm cc'ing the DRI and Mesa lists to see if anyone else has can 
try to reproduce this and perhaps diagnose it.

It's probably a glitch in one of the texture formats that supported by 
the r200.  I can give debugging tips to anyone who wants to look into it.

-Brian



John Lightsey wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi there,
> 
> I've tracked down a bug to the new teximage code you committed to the Mesa CVS 
> on 21 April 2004.  I'm at a loss as to where the actual problem is so I'm 
> hoping you can identify the bug that these pictures illustrate.  These are 
> from Descent Freespace with the only difference in mesa/xc/drm being the mesa 
> teximage patch.
> 
> http://www.nixnuts.net/files/freespace-good.jpg
> http://www.nixnuts.net/files/freespace-bad.jpg
> 
> LIBGL_ALWAYS_INDIRECT=1 results in the text rendering properly.
> 
> I assume this is the same problem mentioned during the weekly dri-devel IRC 
> meeting on 24 May.
> 
> http://www.terraform.ca/missingfonts1.png
> 
> Every version after 21 April 2004 that I've tried has the same problem.
> I'm using a Radeon 8500 running Debian Sid if it makes a difference.
> 
> If you're already aware of this problem or it's source, sorry to have wasted 
> your time.
> 
> Thanks
> 
> John Lightsey
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFAxVR2BYeybkXz+/kRAuSLAKC+ToXiDegcL0I8sL4JiT0l2xb2WACgwBhR
> Eo/4Rh2mkbcmnTzUsBwj1to=
> =3LnD
> -----END PGP SIGNATURE-----
>