<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - protocol: Reporting damage in surface coordinates doesn't work with EGL" href="https://bugs.freedesktop.org/show_bug.cgi?id=78190#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - protocol: Reporting damage in surface coordinates doesn't work with EGL" href="https://bugs.freedesktop.org/show_bug.cgi?id=78190">bug 78190</a> from <a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> Daniel Stone</a> <pre>Of the EGL implementations in the wild that I know about, Mesa always sends infinite co-ordinates, and Mali doesn't implement SwapBuffersWithDamage, so it's a moot point. Vivante don't implement SwapBuffersWithDamage either. There are various single-platform-only implementations around for PowerVR SGX/RGX, some of which do send buffer co-ordinates for damage (I wrote one of them), but as they're generally part of the platform and need updating anyway, rather than distributed to the public at large, I really don't mind breaking those. The Raspberry Pi driver is broken, but that's still in an unmerged branch on GitHub, since it was done on top of the old shim driver; the new driver anholt is writing is based on Mesa, so again will send infinite co-ordinates. So yes, I do agree with Pekka: I don't really see the upside to breaking backwards compatibility, when it benefits approximately no-one.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>