[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:34:24 PST 2016


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

--- Comment #130 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Christopher,

I finished uploading the patches.
I spent pretty much all day working on this issue for Saturday . . .
Please try to boot your system with all the patches applied, and of course, the
patches must be applied in the order they are numbered.
The second patch from the last one has a flaw where anything detected on the
I2C bus 2 is considered VGA capable.
This is the major flaw of the patch, and it is my view that I will have to
rewrite the code completely in order to remedy this situation.
That being said, it does work with my own laptop, so I loaded it for you to
try.
    The last patch is a controversial one where I "nuked" the predefined table
for display output.
It is still in the code, but the code will ignore it for the purpose of
determining which display output will be turned on.
Now the code will go through detecting all known external transmitters /
encoders like VT1632A TMDS transmitter, VT1622 TV encoder, etc. in all VIA
Technologies Chrome-based integrated graphics chipsets (CLE266 through VX900).
I do not know if my laptop has VT1636 LVDS transmitter, but the code appears to
work fine with my laptop.
I would imagine this will cause some problems with some people, but I feel
strongly that OpenChrome needs to stop using a predefined table as soon as
possible.
The UMS code already has support for automatic detection of pretty much all
known external transmitters (VIA Technologies and Chrontel for TV encoding), so
I figured it is about time we stop using that predefined table.

Regards,

Kevin Brace

-- 
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/3c93eb76/attachment.html>


More information about the Openchrome-devel mailing list