<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa opengles Peppa Pig and openggles2 smurfs on Radeon PowerPC and PPC64" href="https://bugs.freedesktop.org/show_bug.cgi?id=99638#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa opengles Peppa Pig and openggles2 smurfs on Radeon PowerPC and PPC64" href="https://bugs.freedesktop.org/show_bug.cgi?id=99638">bug 99638</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>I mean, simply fixing Mesa now to look right without verifying if the other graphics stack components actually got it right too might lead to another breakage later. It is even possible that we have a double confusion on some pixel path making it look right now, but break when one confusion gets fixed. It seems to me that this would need a developer dedicated to fix it across the stack while having access to a BE machine with a recent enough GPU to run GLESv2 or whatever most compositors use.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>