<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - DRM / KMS bootup error on VX900 platform" href="https://bugs.freedesktop.org/show_bug.cgi?id=94473#c67">Comment # 67</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - DRM / KMS bootup error on VX900 platform" href="https://bugs.freedesktop.org/show_bug.cgi?id=94473">bug 94473</a> from <a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> HuangRan</a> <pre>(In reply to Kevin Brace from <a href="show_bug.cgi?id=94473#c65">comment #65</a>) > Hi Frank, > > 2 e-mails got generated automatically, and was sent to openchrome-devel > mailing list. > > <a href="https://lists.freedesktop.org/archives/openchrome-devel/2016-March/002167">https://lists.freedesktop.org/archives/openchrome-devel/2016-March/002167</a>. > html > <a href="https://lists.freedesktop.org/archives/openchrome-devel/2016-March/002168">https://lists.freedesktop.org/archives/openchrome-devel/2016-March/002168</a>. > html > > Frank, great job on analyzing what was going on inside the DRM code, and I > hope to further develop the new DRM module for VIA Technologies IGP with you. Hi Kevin, Sure, no problem. Right now, I am going through the close driver KMS code to check why HDMI is not working with OpenChrome KMS code. By the way, I found that in current close driver, it has a large part of code to get BIOS/vBIOS information for graphics driver to use. And for this part of code, I didn't see OpenChrome DRM/DDX code have that. Based on my experience for RADEON, I really think this part of code should be useful for OpenChrome DRM code because graphic driver need talk to BIOS(VBIOS) to get enough information to do mode setting. Thanks, Frank</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>