<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV34] [NV49] terminal's visual bell is very slow with nouveau" href="https://bugs.freedesktop.org/show_bug.cgi?id=36090#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV34] [NV49] terminal's visual bell is very slow with nouveau" href="https://bugs.freedesktop.org/show_bug.cgi?id=36090">bug 36090</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Looking into EXA a bit, there's a EXASolid impl shared by all pre-nv50 cards. One of the things it apparently doesn't handle are 32-bit visuals with solid draws that include a fancy "op", which I assume the visual bell would, like xor or whatever. I have a hard time believing this restriction holds, so I'm going to try removing it on some cards I have (at some point). If you guys want to play around with it, I'm talking about the if (ppix->drawable.bitsPerPixel == 32) return FALSE; in NV04EXASetROP. Something causing NV04EXAPrepareSolid to return false would definitely explain the fallback to fbSolid.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>