<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NV67] Modesetting failure at 1280x800" href="https://bugs.freedesktop.org/show_bug.cgi?id=70972#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NV67] Modesetting failure at 1280x800" href="https://bugs.freedesktop.org/show_bug.cgi?id=70972">bug 70972</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>All of the modesetting logic (for pre-G80 chips) lives in drivers/gpu/drm/nouveau/dispnv04 This is mostly an adaptation of xf86-video-nv to work in the kernel, with some IMHO misguided "cleanups" that were applied to some of the incomprehensible clock/etc calculation code. Unfortunately those are also mixed in with legit fixes, so it's hard to undo. Either way, since xf86-video-nv also reputedly can't make 1280x800 work, reading that source is unlikely to be of much help. However at least the NV1A and NV1F IGP's tend to have their own very special clock calculation logic, so perhaps that's missing (might look at what e.g. NV4C/NV4E do, as those allegedly work well). There are already traces of both the blob and nouveau and how they perform the modesetting (see attachments in this bug). What's largely missing is identifying what nouveau does differently, and then coming up with a way to fix it. You can use 'demmio' from envytools to help analyze the traces (<a href="https://github.com/envytools/envytools">https://github.com/envytools/envytools</a>). If you have questions about the tooling or the code, feel free to join in #nouveau on irc.freenode.net.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>