We use a graphic board with a radeon chip to drive a 5 megapixel monochrome monitor. Now we recognized that you can't distinguish a difference between pixel-value 0 and pixel-value 1. We changed the method RADEONLoadPalette to trace the palette values we receive from the caller. Here is the output: (II) RADEON(0): Largest offscreen area available: 2048 x 5621 (!!) RADEON(0): RADEONLoadPalette ENTERED (II) RADEON(0): Load Palette: 0 - 0 0 0 (II) RADEON(0): Load Palette: 1 - 0 0 0 (II) RADEON(0): Load Palette: 2 - 1 1 1 (II) RADEON(0): Load Palette: 3 - 2 2 2 (II) RADEON(0): Load Palette: 4 - 3 3 3 (II) RADEON(0): Load Palette: 5 - 4 4 4 (II) RADEON(0): Load Palette: 6 - 5 5 5 (II) RADEON(0): Load Palette: 7 - 6 6 6 (II) RADEON(0): Load Palette: 8 - 7 7 7 (II) RADEON(0): Load Palette: 9 - 8 8 8 (II) RADEON(0): Load Palette: 251 - 250 250 250 (II) RADEON(0): Load Palette: 252 - 251 251 251 (II) RADEON(0): Load Palette: 253 - 252 252 252 (II) RADEON(0): Load Palette: 254 - 253 253 253 (II) RADEON(0): Load Palette: 255 - 254 254 254 (II) RADEON(0): Direct rendering disabled You can see that the palette is "shifted" one step down and the output for index 0 and 1 is zero. That's why we loose the pixel-value 1.
Created attachment 2866 [details] [review] Backport from current CVS Output of the command xdpyinfo.
no content.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.