<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DVI port failure with external TMDS transimitter for T510/T5555/C90LE thin clients" href="https://bugs.freedesktop.org/show_bug.cgi?id=95059#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DVI port failure with external TMDS transimitter for T510/T5555/C90LE thin clients" href="https://bugs.freedesktop.org/show_bug.cgi?id=95059">bug 95059</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to frank from <a href="show_bug.cgi?id=95059#c6">comment #6</a>) Hi Frank, > Created <a href="attachment.cgi?id=124119" name="attach_124119" title="Xorg.0.log of V90LE with UMS 0.4.0">attachment 124119</a> <a href="attachment.cgi?id=124119&action=edit" title="Xorg.0.log of V90LE with UMS 0.4.0">[details]</a> > Xorg.0.log of V90LE with UMS 0.4.0 > > hi,I tried ums0.4.0 in V90LE with DVI port,it can't work,from the > Xorg.0.log,it seems dvi port can't get the edid data correctly,and I found > that in the source code of ddx,the dvi init function has been commented > out(ViaOutputsDetect function in via_outputs.c),so I tried to uncomment > it,then the edid can be read as in the attachments,but the display still > can't work,so my question is that why comment out the via_dvi_init > function,and this function seems just point at vt1632a transmiter,so if the > board has no vt1632,how to init the dvi port? > hope to get the answer. There is a very simple reason why the code that initializes an external TMDS transmitter (i.e., the code that looks for VT1632A via I2C bus) is currently disabled. I simply could not get it to work, so I had to disable it for now. <a href="https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=0748029d3a562283de7aa6120f434a1e80631e05">https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=0748029d3a562283de7aa6120f434a1e80631e05</a> If you noticed it, the next commit I made after the above one was the release of Version 0.4.0. <a href="https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=52730d1da4019969fb4cbd13152ffd06b1ee75e2">https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=52730d1da4019969fb4cbd13152ffd06b1ee75e2</a> The real reasons behind disabling the code that deals with an external TMDS transmitter are the following. Some people needed a newer version of OpenChrome to be bundled with their Linux distributions ASAP (as soon as possible) due to a bug in the previous version (Version 0.3.3) that affect devices that are not registered with a "known device table." <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" href="show_bug.cgi?id=94130#c12">https://bugs.freedesktop.org/show_bug.cgi?id=94130#c12</a> Also, I have been working on trying to improve OpenChrome since July 2015, and I just wanted to release a new version since fixing all the bugs will probably take years. The development process was becoming stressful, and I needed to ship something because I was getting fatigued working on this project. I am okay now, and I continue to work on fixing the code. I will give you more technical explanations as to why DVI via VT1632A is not working yet in another post.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>