<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - drm.edid_firmware override does not work" href="https://bugs.freedesktop.org/show_bug.cgi?id=106291#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - drm.edid_firmware override does not work" href="https://bugs.freedesktop.org/show_bug.cgi?id=106291">bug 106291</a> from <a class="email" href="mailto:haupt.wolfgang@gmail.com" title="Wolfgang Haupt <haupt.wolfgang@gmail.com>"> Wolfgang Haupt</a> <pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=106291#c19">comment #19</a>) > It seems to me the drm.edid_firmware option (that this bug was originally > about) works as expected. Yes we can agree on that one. > Obviously everything about DP link fail when you don't have a cable > connected. I'm not sure what your expectation is. That can't work. I want to force display on digital output and hardcode the edid. May I ask about the "why" it can't work, prior to kernel 4.15 it was possible to use: "initrd=/edid.cpio drm_kms_helper.edid_firmware=DP-1:edid/edid.bin video=DP-1:D" > (In reply to Wolfgang Haupt from <a href="show_bug.cgi?id=106291#c9">comment #9</a>) > > 2. Our GBM kodi implementation needs a valid connector and encoder in order > > to setup rendering, otherwise the application is stopped, I want to > > workaround this by hardcoding the edid. > > I'm turning to this one, and wondering if that's reasonable behavior for > your userspace. We are working towards a better solution already, but it's a huge undertaking and could easily take us another year. As stated above, I was able to workaround this in older kernels.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>