<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#c272">Comment # 272</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:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> HuangRan</a> <pre>Hi Kevin, Yup. Definitely I want to give a try with your new patches. But as I replied in previous information, I can't install Ubuntu/Lubuntu 12.04 on those thin clients! For HP T510, as you said, I have seen SiI164 chip on the board. So do you mean that SiI164 is also an TMDS transmitter chip which is similar as VT1632A and can convert TMDS to DVI-I? So for the first DVI port of T510, if my understanding is correct, it does not using any transmitter. Thanks, Frank > > Wow, you now have several thin clients! > Regarding DVI, you should try the latest code that I just committed for > improved DVI support, but I can say that DVI coming out of VT1632A is fairly > unproven at this point. > This is due to the fact that the code to support it was donated in January > 2015, and I do not think it was tested adequately before it was committed. > That being said, I will be very interested in seeing if it will work with > the current code. > Regarding HP T510, it is VX900 chipset based, so the DVI-I "should" work. > Actually, it appears that HP T510 has another DVI connector (DVI-D), but the > signals come from SiI 164 chip made by Silicon Image. > Many VIA Technologies chipsets have a thing called DVP, (Digital Video Port) > and apparently, SiI 164 is connected to DVP. > At this point, OpenChrome does not support this chip, although SiI 164 and > VT1632A are really register compatible except vendor and device IDs, so we > should be able to support it in the future. > If you read through some comments here, the OpenChrome was not able to > detect SiI 164 through I2C bus.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>