https://bugs.freedesktop.org/show_bug.cgi?id=96785
--- Comment #4 from Kevin Brace <kevinbr...@gmx.com> ---
Hi Xavier,
You can try the patch to see if it makes a difference.
I do not own a board that uses I2C bus 3, so it is still fairly unproven.
As long as EDID is not coming back from the monitor, OpenChrome cannot move
forward, and this is why you do not see anything on the screen.
At my place, I have verified that VT1632A is working with Wyse Vx0 and Cx0 thin
clients.
They both use I2C bus 2 to communicate to VT1632A.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openchrome-devel