<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Redraw lag on Ivy Bridge since 1f6dfc9df678" href="https://bugs.freedesktop.org/show_bug.cgi?id=97914#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Redraw lag on Ivy Bridge since 1f6dfc9df678" href="https://bugs.freedesktop.org/show_bug.cgi?id=97914">bug 97914</a> from <a class="email" href="mailto:john@jlindgren.net" title="John Lindgren <john@jlindgren.net>"> John Lindgren</a> <pre>(In reply to Jean Delvare from <a href="show_bug.cgi?id=97914#c36">comment #36</a>) > I have to admit I'm a bit puzzled. This bug only seems to happen on Ivy > Bridge processors, using the updated intel ddx driver. ... #100408 indicates that Haswell is affected as well. My impression is that most people affected by this bug are switching to the modesetting driver. I did so a couple of months ago. Glamor acceleration gives "good enough" 2D performance, and I haven't seen any similar drawing bugs. I also question blaming Mesa for this since the same version(s) of Mesa is able to run modesetting on the same hardware without issue. Theoretical questions of "whose fault is it" aside, introducing this optimization/regression into the Intel driver without sufficient testing shows a lack of concern on Intel's part for its customers, and I'll take that into account in my next hardware purchase.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>