<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wyse Cx0 No display on DVI with DVI+VGA "Y" adapter." href="https://bugs.freedesktop.org/show_bug.cgi?id=97387#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wyse Cx0 No display on DVI with DVI+VGA "Y" adapter." href="https://bugs.freedesktop.org/show_bug.cgi?id=97387">bug 97387</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>Hi Eric, This is my best current understanding of how DVI-I connector works. DVI-I has both DVI signals and analog VGA signals. However, it has only one I2C bus. Within OpenChrome, when an EDID is obtained from the monitor, the code looks for whether or not the returned EDID is an analog type or digital type. If an analog type is returned, it is safe to assume analog VGA presence. However, if a digital type EDID is returned, it is a little tricky since a digital type EDID can be an LVDS flat panel. (i.e., laptop LCD monitor, not the typical desktop LCD monitor) or DVI. For now, I discontinued the use of I2C bus for LVDS flat panel due to conflicts with DVI code. The LVDS flat panel code is now 100% dependent on BIOS based interface to tell OpenChrome the panel resolution. I do not necessarily like this implementation, but it is what I have now. Some LVDS flat panel do not have an I2C bus coming out of it. I recently updated the flat panel screen resolution table due to this LVDS flat panel and DVI conflict issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>