[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[bugzilla-daemon at freedesktop.org]

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

Kevin Brace <kevinbrace at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #121090|0                           |1
        is obsolete|                            |

--- Comment #140 from Kevin Brace <kevinbrace at gmx.com> ---
Created attachment 121240
  --> https://bugs.freedesktop.org/attachment.cgi?id=121240&action=edit
Reducing the use of a display output table

This update will be a major one for OpenChrome. The use of an internal
predefined display output table for known devices previously used to
initialize display outputs will be reduced. What this means is that
OpenChrome will go through scanning each I2C bus to determine which
display output type is connected before initializing the display.
In practice, the predefined display output table is still used, but
OpenChrome is far less dependent on it. 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 displays. 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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-devel/attachments/20160124/c03b81ea/attachment-0001.html>