[Openchrome-devel] [Bug 96711] K8M800/K8N800 (unsure which): 0.5.0-rc2 gets stuck saturating cpu during basic use

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 1 19:08:32 UTC 2016


--- Comment #9 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Roc,

While I was writing the reply I just posted
(https://bugs.freedesktop.org/show_bug.cgi?id=96711#c8), 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.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160701/e455a0f3/attachment-0001.html>

More information about the Openchrome-devel mailing list