[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91966

--- Comment #272 from HuangRan <huangran at iscas.ac.cn> ---
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.

-- 
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/20160317/d47fd0e7/attachment-0001.html>