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

Kevin Brace <kevinbr...@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevinbr...@gmx.com

--- Comment #11 from Kevin Brace <kevinbr...@gmx.com> ---
Hi Eric,

Sorry for the slow response.
I hate to say this, but after reading the DVI specification looking at the pin
assignment, it appears that there is only one I2C bus per DVI-I connector.
What this means is that if there are 2 devices connected to the DVI-I
connector, the behavior is undefined. (unpredictable)
This is probably why DVI to VGA adapter is used all the time rather than DVI
and VGA "Y" cable, which is very rare.
I will treat this as something I will consider "unsupported," but obviously, I
will not try to write code that will undermine the use of the a DVI and VGA "Y"
cable.
    Since I did major rewriting of DVI related code and I do not have access to
Wyse Cx0 for now (I still own it, obviously.), I wanted to see how the new code
fared.
Regarding the "DVI-2" display you observed, that one is my laziness (i.e., it's
a feature, not a bug) where I hardcoded "DVI-2" into the code for now.
I am planning to make this numbering programmable, so that it can correctly
display "DVI-1," "DVI-2," etc.
As a general rule, an integrated TMDS transmitter will always be assigned
(i.e., "DVI-1") before external TMDS transmitters are assigned as "DVI-2,"
"DVI-3," etc.
I will definitely fix this before the official OpenChrome Version 0.6 release.
I will start working on this in the next few days so that it does not linger
any longer.
    Regarding the DVI code, there is still some code where I am still
hardcoding settings that make it work with mainly Wyse Vx0 thin client. (i.e.,
I am assuming VT1632A is located at DVP0.)
I will like to make this general purpose since this situation is not desirable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openchrome-devel

Reply via email to