<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c139">Comment # 139</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>Created <a href="attachment.cgi?id=121239" name="attach_121239" title="Determine the interface type for VGA detection">attachment 121239</a> <a href="attachment.cgi?id=121239&action=edit" title="Determine the interface type for VGA detection">[details]</a> <a href='page.cgi?id=splinter.html&bug=91966&attachment=121239'>[review]</a> Determine the interface type for VGA detection The previous version of the code that took into consideration using I2C bus 1 and 2 to obtain EDID did not examine whether or not the monitor connected to is a digital or analog type. Since I2C bus 2 is often connected to a digital type interface, this meant that VGA monitor detection code was misdetecting the connected output type if I2C bus 1 did not detected a monitor (i.e., VGA monitor), but I2C bus 2 detected a monitor (likely a DVI monitor or LVDS flat panel). Now the code will look to see if the connected type is an analog type interface before recognizing it as a likely VGA monitor.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>