<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><base href="https://bugs.freedesktop.org/"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:宋体;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:宋体;}
pre
{mso-style-priority:99;
mso-style-link:"HTML 预设格式 Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:宋体;}
span.vcard
{mso-style-name:vcard;}
span.fn
{mso-style-name:fn;}
span.HTMLChar
{mso-style-name:"HTML 预设格式 Char";
mso-style-priority:99;
mso-style-link:"HTML 预设格式";
font-family:"Courier New";}
span.quote
{mso-style-name:quote;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1193148805;
mso-list-template-ids:-474582262;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kevin,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'> Glad to receive your response so quickly.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'> For I2C probe EDID information, generally there are several the I2C HW pair lines as you said. And they can be routed to VGA connector/DVI connector, even for HDMI connector. It depends on HW schematic. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'> So for this Wyse C90LE case, do we know which I2C HW pair lines are used for chipset? If there is no EDID information probed out, we can try a fixed mode to see if that is the reason for this issue. I know how to do it in DRM instead of UMS driver. And I think there is a way to try a fixed mode in UMS driver too.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Frank<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt'>发件人<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> Openchrome-devel [mailto:openchrome-devel-bounces@lists.freedesktop.org] </span><b><span style='font-size:10.0pt'>代表 </span></b><span lang=EN-US style='font-size:10.0pt'>bugzilla-daemon@freedesktop.org<br></span><b><span style='font-size:10.0pt'>发送时间<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> 2016</span><span style='font-size:10.0pt'>年<span lang=EN-US>2</span>月<span lang=EN-US>22</span>日<span lang=EN-US> 17:36<br></span><b>收件人<span lang=EN-US>:</span></b><span lang=EN-US> openchrome-devel@lists.freedesktop.org<br></span><b>主题<span lang=EN-US>:</span></b><span lang=EN-US> [Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics<o:p></o:p></span></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal><b><span lang=EN-US><a href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c202" title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics">Comment # 202</a> on <a href="https://bugs.freedesktop.org/show_bug.cgi?id=91966" title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics">bug 91966</a> from <span class=vcard><a href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"><span class=fn>Kevin Brace</span></a> </span></span></b><span lang=EN-US><o:p></o:p></span></p><pre><span lang=EN-US>(In reply to HuangRan from <a href="show_bug.cgi?id=91966#c201">comment #201</a>)<o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span lang=EN-US>Hi Frank,<o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span class=quote><span lang=EN-US>> Hi Guys,<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> Returning from my holiday and looking at this thread from the start to<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> the end takes me several hours to do so although I have to skip some content<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> for your chat becuase it is so long.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> As I replied the mail to Kevin, I prefer to put my more time on<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> OpenChrome and has several guys invovled on this project. So I hope I can<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> provide some useful informaiton on this bug too.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> So is this bug fixed or not? Does I2C 2 probe EDID information from DVI<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> interface?<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> Thanks,<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>> Frank</span></span><span lang=EN-US><o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span lang=EN-US>The way the code works right now with the patch is that I2C bus 1 and 2 are<o:p></o:p></span></pre><pre><span lang=EN-US>used for VGA related monitor detection.<o:p></o:p></span></pre><pre><span lang=EN-US>xserver's API returns a structure that tells the caller if the monitor type is<o:p></o:p></span></pre><pre><span lang=EN-US>analog or digital.<o:p></o:p></span></pre><pre><span lang=EN-US>I use this information to see if I2C bus 1 or 2 is connected to an analog<o:p></o:p></span></pre><pre><span lang=EN-US>monitor (i.e., VGA monitor).<o:p></o:p></span></pre><pre><span lang=EN-US>I read the Intel DDX UMS code, and they apparently do this.<o:p></o:p></span></pre><pre><span lang=EN-US>As for DVI, I2C bus 2 or 3 are used for communicating with the monitor and an<o:p></o:p></span></pre><pre><span lang=EN-US>external TMDS transmitter chip.<o:p></o:p></span></pre><pre><span lang=EN-US>In other words, I2C bus 2 can be used for VGA, DVI, or even a TV encoder chip.<o:p></o:p></span></pre><pre><span lang=EN-US>The code that handles an external TMDS transmitter for DVI (i.e., VT1632A chip)<o:p></o:p></span></pre><pre><span lang=EN-US>is still relatively unproven.<o:p></o:p></span></pre><pre><span lang=EN-US>It was donated in early 2015, but there was a bug in it, and I help fix it with<o:p></o:p></span></pre><pre><span lang=EN-US>the person who reported it (<a href="show_bug.cgi?id=93675" title="RESOLVED FIXED - Segfault in xf86DestroyI2CDevRec">Bug 93675</a>).<o:p></o:p></span></pre><pre><span lang=EN-US>I do own about 10 or so VIA Technologies IGP based mainboards / computers at my<o:p></o:p></span></pre><pre><span lang=EN-US>place, but I do not really have a functional mainboard / computer with DVI<o:p></o:p></span></pre><pre><span lang=EN-US>coming out of it at this point that is not a thin client.<o:p></o:p></span></pre></div><div class=MsoNormal align=center style='text-align:center'><span lang=EN-US><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=EN-US>You are receiving this mail because: <o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span lang=EN-US>You are the assignee for the bug.<o:p></o:p></span></li></ul></div></div></body></html>