<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - modesetting driver plus DRI3 causes extremely slow scrolling with WebKitGTK+ in accelerated compositing mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=85064#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - modesetting driver plus DRI3 causes extremely slow scrolling with WebKitGTK+ in accelerated compositing mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=85064">bug 85064</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Dave Airlie from <a href="show_bug.cgi?id=85064#c37">comment #37</a>) > 00:50 < keithp> So, they can't use a pixmap because GL sucks, I assume > 00:50 < airlied> yeah most likely a GL suckage [Citation needed] Why exactly can't they use pixmaps for this? > 00:53 < keithp> DRI2 behaviour used to be unthrottled entirely > 00:53 < keithp> you'd get infinite FPS > 00:54 < keithp> which kinda sucked when the screen saver fired and your > CPU/GPU utilization went to 100% Actually, the DRI2 behaviour depends on the driver. The -ati/amdgpu drivers probably synchronize to the same CRTC as with DRI3, and extrapolate the refresh timings using timers while the CRTC is off.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>