Re: [Dri-devel] r128 textures
On Tue, 16 Jul 2002, Henry Worth wrote: Have there been any reports of r128 texture color problems on x86 with recent CVS? Or that it even works? I just updated to today's build and texture colors look fine on r128 in x86. Also, we had reports that the changes made in Mesa on the trunk (which we merged into the mach64 branch) fixed textures on ppc for mach64, which has a choose texture function based on r128. -- Leif Delgass http://www.retinalburn.net --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] r128 textures
Leif Delgass wrote: On Tue, 16 Jul 2002, Henry Worth wrote: Have there been any reports of r128 texture color problems on x86 with recent CVS? Or that it even works? I just updated to today's build and texture colors look fine on r128 in x86. Also, we had reports that the changes made in Mesa on the trunk (which we merged into the mach64 branch) fixed textures on ppc for mach64, which has a choose texture function based on r128. Since the merge, the radeon PPC fixes added an additional swap in the texture path for BE systems. But, the texutil code already appear to have been endian aware and the radeon patches also appear to be fighting the endiness, and color ordering, neutral formating in tnl_dd_vertex.h by using arrays instead of the named color fields. Since x86 r128 is working, I'm going to prep my patches with the PACK*LE changes reverted. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] r128 textures
On Wed, 2002-07-17 at 00:34, Henry Worth wrote: Leif Delgass wrote: On Tue, 16 Jul 2002, Henry Worth wrote: Have there been any reports of r128 texture color problems on x86 with recent CVS? Or that it even works? I just updated to today's build and texture colors look fine on r128 in x86. Also, we had reports that the changes made in Mesa on the trunk (which we merged into the mach64 branch) fixed textures on ppc for mach64, which has a choose texture function based on r128. Since the merge, the radeon PPC fixes added an additional swap in the texture path for BE systems. If I understand correctly, the endianness fixes are the Mesa changes Leif referred to. But, the texutil code already appear to have been endian aware It wasn't. One might argue that it still isn't, but it definitely wasn't before. :) and the radeon patches also appear to be fighting the endiness, and color ordering, neutral formating in tnl_dd_vertex.h by using arrays instead of the named color fields. I don't understand what you're talking about. A lot of my fixes have been exactly to get rid of fixed offsets into char arrays. Since x86 r128 is working, I'm going to prep my patches with the PACK*LE changes reverted. Looking forward to your patches, it's hard for me to understand without seeing the changes you're making to the code. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] r128 textures
On 17 Jul 2002, Michel Dänzer wrote: I just updated to today's build and texture colors look fine on r128 in x86. Also, we had reports that the changes made in Mesa on the trunk (which we merged into the mach64 branch) fixed textures on ppc for mach64, which has a choose texture function based on r128. Since the merge, the radeon PPC fixes added an additional swap in the texture path for BE systems. If I understand correctly, the endianness fixes are the Mesa changes Leif referred to. Right. The merge from the trunk to the mach64 branch was done June 26 -- after the endianess fixes. -- Leif Delgass http://www.retinalburn.net --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] r128 textures
Leif Delgass wrote: On 17 Jul 2002, Michel Dänzer wrote: I just updated to today's build and texture colors look fine on r128 in x86. Also, we had reports that the changes made in Mesa on the trunk (which we merged into the mach64 branch) fixed textures on ppc for mach64, which has a choose texture function based on r128. Since the merge, the radeon PPC fixes added an additional swap in the texture path for BE systems. If I understand correctly, the endianness fixes are the Mesa changes Leif referred to. Right. The merge from the trunk to the mach64 branch was done June 26 -- after the endianess fixes. 1 I can find no extra byte swapping being done to textures in the r128 code and dword swaps at later point in the pipeline would break 16 and 8 bpp textures. 2 The r128 texture code works without PACK*LE works on both LE and BE systems in both 32bpp and 16bpp. None of the code I had to change except the PACK*LE would affect textures. 3 Any change that I can see to make to work with the PACK*LE would have to be conditional on endiness to not break x86. But that would be redundant! 4 Something is wrong, but where? --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
