<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - K8M800/K8N800 (unsure which): 0.5.0-rc2 gets stuck saturating cpu during basic use" href="https://bugs.freedesktop.org/show_bug.cgi?id=96711#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - K8M800/K8N800 (unsure which): 0.5.0-rc2 gets stuck saturating cpu during basic use" href="https://bugs.freedesktop.org/show_bug.cgi?id=96711">bug 96711</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>Hi Roc, While I was writing the reply I just posted (<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - K8M800/K8N800 (unsure which): 0.5.0-rc2 gets stuck saturating cpu during basic use" href="show_bug.cgi?id=96711#c8">https://bugs.freedesktop.org/show_bug.cgi?id=96711#c8</a>), you posted a message. Anyway, I am glad that the issue is resolved for now. This will mean that the major obstacles for releasing OpenChrome Version 0.5 is gone, and I will only have to do a few more commits related to DVI transmitter chip support (VT1632A). I am in the process of adding lines of code to takeover the initialization of more and more of the VIA IGP registers, in order to do away with the shadow use of viafb. As you saw from the bug you experienced, it takes time to get the register combination right since VIA had 11 different generations of IGP, and even within the same chipset, depending on the way the hardware vendor implemented the device, behavior changes. Plus, for many of their chipsets, they never released hardware programming documents without an NDA. So please be patient regarding the viafb issue. I am still working on it since I will like to resolve the instability of ACPI S3 State resume for my own use.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>