<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#c129">Comment # 129</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=121090" name="attach_121090" title="Discontinuing the use of a predefined display output table">attachment 121090</a> <a href="attachment.cgi?id=121090&action=edit" title="Discontinuing the use of a predefined display output table">[details]</a> <a href='page.cgi?id=splinter.html&bug=91966&attachment=121090'>[review]</a> Discontinuing the use of a predefined display output table This update will be a major one for OpenChrome. The internal predefined display output table previously used to initialize display outputs is no longer going to be used except for OLPC XO-1.5. This means that OpenChrome will go through scanning each I2C bus to determine what display output type is connected before initializing the display. This is a highly risky update that will likely break OpenChrome for some users. However, the general trend of computing industry has been going in the direction of automatically detecting and configuring connected display devices, and because of this, it is author's view that OpenChrome needs to stop relying on an outdated concept like the use of a predefined table to figure out which display output should be initialized. The compiled device driver was tested on the following computer. - Epic 1314 laptop (MSI VR321 laptop equivalent, VN896 chipset) with Lubuntu 12.04 i386</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>