<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - gl_renderer: poor error messages when config matching fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=89385#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - gl_renderer: poor error messages when config matching fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=89385">bug 89385</a> from <a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> Daniel Stone</a> <pre>(In reply to Bruno from <a href="show_bug.cgi?id=89385#c2">comment #2</a>) > I'm fine with a "copy" of gl_renderer to handle older hardware. That one > would not need any fancyness (so no need for extra shadows, bluring or > whatever effects, except simple argb transparency). > Software rendering is rather (very) slow. Hmm, the problem is that it's not just a copy, but in fact a near-total rewrite of the renderer, since we operate everything with shaders rather than the fixed-function pipeline from GLESv1. Given that this is a pretty extreme corner-case, I honestly wouldn't hold your breath to see this happen: it's not a priority at all upstream.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>