<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - "*ERROR* Failed to probe lspcon" when HDMI isn't plugged before boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=109112#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - "*ERROR* Failed to probe lspcon" when HDMI isn't plugged before boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=109112">bug 109112</a> from <a class="email" href="mailto:kai.heng.feng@canonical.com" title="Kai-Heng Feng <kai.heng.feng@canonical.com>"> Kai-Heng Feng</a> <pre>(In reply to Swati Sharma from <a href="show_bug.cgi?id=109112#c28">comment #28</a>) > (In reply to Kai-Heng Feng from <a href="show_bug.cgi?id=109112#c3">comment #3</a>) > > I also tested Windows 10. HDMI still works when the cable wasn't plugged > > before boot. > > Hi Kai-Heng Feng, > > If we go by theory, there is no 1:1 mapping of Windows and Linux driver > architecture. Design for lsp-con is different in both. In Windows, you are > able to probe lsp-con because during hotplug windows drivers reinitialize > all the connectors whereas in linux, connectors are initialized only once. > It means during boot time, if lspcon is not probbed..we won't be able to > probe it during hotplug. I understand Linux and Windows driver are quite different. My point was, whether lspcon firmware has a bug or not is moot - software alone can make it work, or at least workaround it. > > Since I am not having the same setup, I can't reproduce the issue. Give me > some time so that I can arrange for the setup and get back to you. Sure, thanks for your effort.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>