<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - gm107 font glitches with kernel 4.1rc" href="https://bugs.freedesktop.org/show_bug.cgi?id=90932#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - gm107 font glitches with kernel 4.1rc" href="https://bugs.freedesktop.org/show_bug.cgi?id=90932">bug 90932</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Marcus Moeller from <a href="show_bug.cgi?id=90932#c7">comment #7</a>) > Shouln't this be fixed in nouveau instead of moving to another driver? Or is > this just a suggestion for a workaround? The fix in nouveau will be "remove glamor integration" and "fail to load for GM107+". But we haven't fully decided on that *quite* yet. And I have an EXA impl in the works for GM107, so perhaps we'll use that. TBD. The problem that you're seeing is with glamor, and they changed the way font rendering was done in X 1.17, which is why I'm suggesting you use that. Separate from that, nouveau's integration with glamor is totally fubar'd and should be removed, as per the above, but that has nothing to do with any misrendering you might see. For example perhaps you might observe the lack of a GLX_ARB_create_context_profile. This is a symptom of DRI2 support basically missing, which is going to cause major problems. Since nouveau's integration with glamor would be no different from modesetting's integration with glamor, might as well just use that directly... [There are one or two things nouveau can still do that modesetting can't, but those differences are in the process of being eliminated.]</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>