[Openchrome-devel] [Bug 96785] CN700 + VT1632 doesn't detect screen on DVI port

[bugzilla-daemon at freedesktop.org]

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

Kevin Brace <kevinbrace at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevinbrace at gmx.com

--- Comment #1 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Xavier,

If you read the log carefully, you can see that I2C bus 3 is seeing VT1632A.

________________________________________________________________________
. . .

[   380.402] (II) CHROME(0): Entered via_dvi_init.
[   380.402] (--) CHROME(0): Will probe I2C Bus 3 for a possible external TMDS
transmitter.
[   380.402] (II) CHROME(0): I2C device "I2C Bus 3:VT1632A" registered at
address 0x10.
[   380.402] (II) CHROME(0): Entered via_vt1632_probe.
[   380.404] (II) CHROME(0): Vendor ID: 0x1106
[   380.409] (II) CHROME(0): Device ID: 0x3192
[   380.414] (--) CHROME(0): VT1632A DVI transmitter detected.
[   380.414] (II) CHROME(0): Exiting via_vt1632_probe.
[   380.414] (II) CHROME(0): Entered via_vt1632_init.
[   380.418] (II) CHROME(0): VT1632A Dot Clock Range: 25 to 165 MHz
[   380.418] (II) CHROME(0): Entered via_vt1632_dump_registers.
[   380.418] (II) CHROME(0): VT1632A: dumping registers:
[   380.419] (II) CHROME(0): VT1632A: 0x00: 0x06
[   380.421] (II) CHROME(0): VT1632A: 0x01: 0x11
[   380.426] (II) CHROME(0): VT1632A: 0x02: 0x92
[   380.431] (II) CHROME(0): VT1632A: 0x03: 0x31
[   380.433] (II) CHROME(0): VT1632A: 0x04: 0x00
[   380.434] (II) CHROME(0): VT1632A: 0x05: 0x00
[   380.435] (II) CHROME(0): VT1632A: 0x06: 0x19
[   380.436] (II) CHROME(0): VT1632A: 0x07: 0x64
[   380.444] (II) CHROME(0): VT1632A: 0x08: 0x3b
[   380.447] (II) CHROME(0): VT1632A: 0x09: 0x06
[   380.448] (II) CHROME(0): VT1632A: 0x0a: 0x00
[   380.449] (II) CHROME(0): VT1632A: 0x0b: 0x00
[   380.450] (II) CHROME(0): VT1632A: 0x0c: 0x00
[   380.455] (II) CHROME(0): VT1632A: 0x0d: 0x80
[   380.457] (II) CHROME(0): VT1632A: 0x0e: 0x00
[   380.460] (II) CHROME(0): VT1632A: 0x0f: 0x00
[   380.460] (II) CHROME(0): Exiting via_vt1632_dump_registers.
[   380.460] (II) CHROME(0): Exiting via_vt1632_init.
. . .
________________________________________________________________________


Furthermore, it is detecting the presence of DVI.

________________________________________________________________________
. . .
[   380.517] (II) CHROME(0): Entered via_vt1632_detect.
[   380.520] (II) CHROME(0): VT1632A: DVI device is detected.
[   380.520] (II) CHROME(0): Exiting via_vt1632_detect.
[   380.520] (II) CHROME(0): I2C device "I2C Bus 3:ddc2" registered at address
0xA0.
[   380.529] (II) CHROME(0): EDID for output DVI-1
[   380.529] (II) CHROME(0): Output VGA-1 disconnected
[   380.529] (II) CHROME(0): Output TV-1 disconnected
[   380.529] (II) CHROME(0): Output DVI-1 disconnected
[   380.529] (WW) CHROME(0): No outputs definitely connected, trying again...
[   380.529] (II) CHROME(0): Output VGA-1 disconnected
[   380.530] (II) CHROME(0): Output TV-1 disconnected
[   380.530] (II) CHROME(0): Output DVI-1 disconnected
[   380.530] (WW) CHROME(0): Unable to find connected outputs - setting
1024x768 initial framebuffer
. . .
________________________________________________________________________


This appears to be EDID is not being returned properly to the host (i.e., CN700
chipset).
If you have a "true" DVI input monitor, that might be a better equipment to
test against.

-- 
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/20160703/3ac519b3/attachment.html>