<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI port is not working on current KMS driver with VX900 platform" href="https://bugs.freedesktop.org/show_bug.cgi?id=94528#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - HDMI port is not working on current KMS driver with VX900 platform" href="https://bugs.freedesktop.org/show_bug.cgi?id=94528">bug 94528</a> from <a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> HuangRan</a> <pre>(In reply to HuangRan from <a href="show_bug.cgi?id=94528#c5">comment #5</a>) > Hi Kevin, > > I tried VX900 closed driver from the download link you provided and see > HDMI port and VGA port are working fine on my platform. So I believe the > closed driver can also work for your VX900 board at least for HDMI port. You > can give a try on that. > Currently I see via_chrome9.ko file from close driver is used by kernel. > And this ko file are compiled from close driver source files. > > Thanks, > Frank Hi Kevin, A correction for my comments above, I can see when VGA port is used, the Xserver can go into desktop and X log shows everything is working fine. For HDMI, it can do mode setting correctly only enter into command mode instead of graphics mode and X log shows it still probing VGA edid information which is not correct. If you have time to give a try on closed driver, let's see what happens at your side, especially for DP port and HDMI port. By the way, you should use a old kernel, i.e., 3.1.10 to compile the closed driver for VX900 which is a requirement for that driver. Thanks, Frank</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>