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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jan 17 02:20:55 PST 2016


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

--- Comment #129 from Kevin Brace <kevinbrace at gmx.com> ---
Created attachment 121090
  --> https://bugs.freedesktop.org/attachment.cgi?id=121090&action=edit
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

-- 
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/20160117/bf8a07f7/attachment.html>


More information about the Openchrome-devel mailing list