Michel Dänzer wrote: > On Thu, 2006-09-21 at 16:15 +0100, Keith Whitwell wrote: >> OK, so as you suggested, it looks like type_endian_mapping should be >> identity for this case, as in the attached diff -- what happens next? > > from 1908/GL_RGBA to 1907/GL_RGB map 0 1 2 4 4 5 > from 1907/GL_RGB to 1908/GL_RGBA map 0 1 2 5 4 5 > i=0, srctype2ubyte_le[i]=0, src2base[i]=0, base2rgba[i]=0, rgba2dst[i]=3, > swap[i]=0 > i=1, srctype2ubyte_le[i]=1, src2base[i]=1, base2rgba[i]=1, rgba2dst[i]=0, > swap[i]=1 > i=2, srctype2ubyte_le[i]=2, src2base[i]=2, base2rgba[i]=2, rgba2dst[i]=1, > swap[i]=2 > i=3, srctype2ubyte_le[i]=3, src2base[i]=4, base2rgba[i]=5, rgba2dst[i]=2, > swap[i]=3 > map 5 0 1 2 > pixelFormats failed at pixel (0,0), color channel 0: > Expected: 0xff 0x00 0x00 0x00 > Found: 0x00 0xff 0xff 0x00 > Format: GL_RGBA > Type: GL_UNSIGNED_BYTE > Internal Format: 3
OK, that's kooky. I guess I haven't got a handle on the problem yet for bigEndian, it may be that there's another conversion needed on the back end. Keith ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
