<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#c301">Comment # 301</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 HuangRan from <a href="show_bug.cgi?id=91966#c299">comment #299</a>) Hi Frank, > Hi Kevin, > > That's true. for LVDS, sometimes, there is no I2C bus. So there is no need > for EDID probe. The resolution information sometimes is in BIOS(vBIOS > table). So the graphics driver just need try to get that from BIOS and do > the mode setting. > I have not gotten such a board which has the LVDS interface to try. > By the way, in next few days, I will spend some time on current HDMI issue > for KMS driver. Stay tuned... > > Thanks, > Frank Okay, some times I do have to disappear for several days to get something done. This is why I sometimes do not reply to your comments for several days. Sorry about that. Anyway, after researching what to do with the LVDS flat panel automatic detection issue, I believe I came up with a good enough solution. Apparently, VIA uses scratch pad registers in their CRT register section to pass the presence of a flat panel and what native resolution the panel supports (I will call this panel ID.). They allow the user to alter these values via BIOS setup (I have several mainboards that support this feature.), and in fact, the code they have written actually uses these feature. I was reading James Simmons' DRM code, and in fact, that is what is happening. I already experimented with the panel ID, and it works with my netbook that comes with an 800 X 480 screen resolution flat panel. I will write the code to figure out the presence of a flat panel tomorrow (a few lines of code), and hope to commit it in the next few days. Okay, is the mouse cursor working with the DVI coming from VT1632A? Eric was reporting that it was not showing up on the screen. If it works, I will not disable the use of it (I was thinking of disable the use of for Version 0.4.0 release for the sake of stability.). Assuming there aren't any more serious issues, I might be able to release OpenChrome Version 0.4.0 within a month. Since I have a good enough solution for the flat panel detection, and this was the culprit of causing display detection issues within the past few weeks, assuming that the solution works, there will not be a Version 0.3.4 release. When I think we are reaching a RC (Release Candidate) stage, I will send out an e-mail about it so that interested people can test the code before the official release. In the future, the version number will go up faster, especially the patch level number (i.e., Version 0.4.("patch level")).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>