<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [r300g] Visuals not found in (default) depth = 24" href="https://bugs.freedesktop.org/show_bug.cgi?id=71789#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [r300g] Visuals not found in (default) depth = 24" href="https://bugs.freedesktop.org/show_bug.cgi?id=71789">bug 71789</a> from <a class="email" href="mailto:maraeo@gmail.com" title="Marek Olšák <maraeo@gmail.com>"> Marek Olšák</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=71789#c29">comment #29</a>) > That piglit sanity is failing with the patch may confirm my suspicion that > something doesn't add up yet I'm afraid: Since the kernel driver and > xf86-video-ati EXA code are using the same hardware formats for > display/rendering with BE & LE, I was wondering how the patch could result > in both display and glReadPixels working correctly for winsys buffers. Looks > like indeed only display works correctly, which indicates that the GPU is > effectively writing/reading PIPE_FORMAT_x8R8G8B8_* pixels like > PIPE_FORMAT_B8G8R8x8_* (which is what the kernel driver and EXA code are > using). The patch is correct from the LE perspective. It simply adds ARGB support and was tested thoroughly on LE. The side effect is that BE can use the format now too, but there may be other issues with BE.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>