> > My read of the current source tree is that there is no generic > support for 16,24,32-bit reverse-endian pixfmts. 24 will require > it's own renderer, but if we were to add a color_r.so we should > be able to provide support for 16 and 32 with just that (assuming > the fb base pointer is aligned, a relatively safe assumtion in > the majority of cases.) > > Am I missing anything, or does this sound like the way to go?
Doesn't the pixfmt's bit masks/shifts already include reversed endian support? > (Christoph -- the old X code may imply that ImageByteOrder is > something you set, but to me it looks as if it's something that > is carved in stone. I don't know. I haven't looked deeply enough in the X code. > It may take a color_r lib to get correct colors on your XCeed server.) Only the old Xlib-target is affected by wrong endianess assumption (little endian machine == LSBFirst). The old X-target works ok. BTW: Correct spelling is "Exceed" :-) -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
