<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [i915][BYT] Blank screen on DSI panel" href="https://bugs.freedesktop.org/show_bug.cgi?id=101205#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [i915][BYT] Blank screen on DSI panel" href="https://bugs.freedesktop.org/show_bug.cgi?id=101205">bug 101205</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>The VBT for the non-working Pipo X8S does not seem to have any real contents in the MIPI DSI sequence block, which is surprising. I can think of two scenarios here: 1) You've changed the boot mode when installing. It's surprisingly common that the VBT is different for UEFI vs. legacy boot. Though this is usually more of an issue on Windows based machines, not sure about Android. (But I guess this is originally dual boot?) 2) The vendor failed to make the panel work using the VBT sequences, and opted to hack it all in the driver. It's usual that the vendor kernels have quite a bit of delta from upstream. You could try to find the sources for the kernels used in both devices, and compare. In any case effectively reverse engineering this kind of non-standard, typically one-off products is not a priority in the upstream driver. If it works, great. If you figure out how to make it work, and contribute upstream, great. But we won't go out of our way to fix this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>