<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - glReadPixels on Intel N3700 (Braswell) slower than Raspberry Pi" href="https://bugs.freedesktop.org/show_bug.cgi?id=99247#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - glReadPixels on Intel N3700 (Braswell) slower than Raspberry Pi" href="https://bugs.freedesktop.org/show_bug.cgi?id=99247">bug 99247</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Pierre Proske from <a href="show_bug.cgi?id=99247#c9">comment #9</a>) > Thanks for investigating! > > I'm happy to use RGBA if that is the fastest path, I had no idea RGB was so > troublesome. Yeah... Turns out that hardware really likes pixels to have nicely aligned addresses. > It would still be great to see this fixed but if I can immediately get > better fps using RGBA then I will do that :) Even if we get faster RGB paths implemented, they won't be as fast as RGBA. So you're probably better off doing RGBA anyway. Specifically, you probably want to use GL_UNSIGNED_BYTE and GL_RGBA in your glReadPixels call. If you ask for the data to be returned in RGB then we have to pack it and that's slow.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>