<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130">bug 94130</a> from <a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> HuangRan</a> <pre>Hi Kevin, Do you mean that 0.3.4 and 0.4.0 will not support VT1632A support with DVI port? And as I reported in 91966 bug, right now my V90LE still not work with VGA and DVI ports both with latest git repository code. So for which commit id of UMS driver, I can use for V90LE? Please let me know it and verify it before you make 0.3.4 release. Thanks, Frank (In reply to Kevin Brace from <a href="show_bug.cgi?id=94130#c14">comment #14</a>) > Hi everyone, > > I can go with the idea of releasing OpenChrome Version 0.3.4, but I will say > that I will need to reverse last several commits I have made. > This is what it will mean. > > - The large known device table will stay (only for Version 0.3.4) > - VBE mode setting will stay (only for Version 0.3.4) > - "Legacy" mode setting will stay (only for Version 0.3.4) > - Benno's patch (<a class="bz_bug_link bz_status_NEW " title="NEW - fix compilation after recent rename" href="show_bug.cgi?id=94660">Bug 94660</a>) will get incorporated > - Drop support for VT1632A external TMDS transmitter for now > (it does not work) > > If this sounds okay, I can release OpenChrome Version 0.3.4 within two weeks. > Of course, this assumes that I do not run into Git related tool usage issue. > After that, I will return to "regularly scheduled program already in > progress," and remove the following items from the master branch source code. > > - The large known device table > - VBE mode setting option > - "Legacy" mode setting option > > That version will be called OpenChrome Version 0.4.0, and all future > development work will revolve around this version. > I do not plan to make any more fixes to Version 0.3.4 branch code since it > is broken in many ways. > I hope to get VT1632A support back for something like Version 0.4.1 or 0.4.2. > I will also like to support Silicon Image SiI 164 for that future version. > Regarding VT1632A support, all I will do for now is OpenChrome will not > initialize it. > The code will stay, but via_dvi_init will not be called, making it > effectively inactive. > Let me know how all of you think.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>