[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 #269 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to HuangRan from comment #261)

Hi Frank,

> Hi Kevin/All,
> 
>    Yesterday, I received several thin clients which I bought two weeks ago
> as I said. That includes Wyse V90LE(VX700), Wyse C90LE(VX855) and HP
> T510(VX900). Attached is the picture for your reference. 
>    For those boards, the same aspect for those boards is that they had DVI-I
> interface(VGA+DVI-D). Especially for HP T510 board, it has an "DVI-I +
> DVI-D" dual ports.
>    I thought for this issue, Kevin have helped solve the "no output" with
> current UMS driver for DVI port, so can you let me know which commit id can
> work for current DVI-I port? 
>    I see that both of Wyse V90LE and Wyse C90LE boards have an VT1632A TMDS
> transmitter on it. And for HP T510 board, it does not have such an
> transmitter chip. So which patch is working for which chip?
> 
> 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/20160316/36c0b0dc/attachment.html>