<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c111">Comment # 111</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to Christopher from <a href="show_bug.cgi?id=91966#c110">comment #110</a>) Hi Christopher, > Kevin, I apologize if I haven't been openly thankful enough here -- but I > really am -- you are doing a GREAT job of helping me, so far, and I do not > want you to give up. > > If I'm the only one in the world with a working OpenChrome driver for VX855 > -- fine by me. If the devs don't care enough to support their own creation, > that's *their* problem. It's not mine, and I don't think it ought to be > yours, either. > > Let's do what we can, and if it becomes apparent that a fork is necessary, > we might consider that as well. Thank you very much for the words of encouragement. I will continue working on fixing the bug you observed and a few more I know exists (i.e., ACPI S3 State resume LVDS DFP screen disappearance bug I am still trying to fix it up completely.). Yeah, it has been pretty discouraging when I have been able to get my patches committed to the public Git repository. I have sent e-mails to several more senior xorg developers (both work at RedHat), so hopefully after a few days (i.e., many people do not resume work probably until January 4th), someone will intervene, and resolve the matter. Just to let you know, starting sometime around February, I may have to reduce my time I spend on OpenChrome probably until late May. Regarding what I have been working on for the past few days, I have been trying to disable the use of display output availability predefined table, and see what happens. Actually, disabling this table is not terribly difficult, but when I do this, even my laptop appears to have issues with screen detection. Ideally, screen detection should be done dynamically via polling 2 to 3 I2C buses available on various VIA Technologies chipsets (One for VGA, one or two for DFP and or TV.). I am now studying how the screen detection and I2C bus polling portion of the code works. I am working on this section because I strongly suspect (although I can be totally wrong) OpenChrome with your computer does not work correctly due to a problem with I2C bus, and in particular, I2C bus #2 and #3 (I2C bus #1 is for VGA. The I2C bus for VGA is typically called VESA DDC.) Regards, Kevin Brace</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>