<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [REGRESSION][BISECT] Linux 4.8: SKL DMC Version is now 1.23?" href="https://bugs.freedesktop.org/show_bug.cgi?id=97182#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [REGRESSION][BISECT] Linux 4.8: SKL DMC Version is now 1.23?" href="https://bugs.freedesktop.org/show_bug.cgi?id=97182">bug 97182</a> from <a class="email" href="mailto:direx@betriebsdirektor.de" title="Direx <direx@betriebsdirektor.de>"> Direx</a> <pre>(In reply to Rodrigo Vivi from <a href="show_bug.cgi?id=97182#c12">comment #12</a>) > Nope, we cannot remove the symbolic link for the same reason that we cannot > remove the 1.23, because there are stable kernel out there that loads that > directly. Most (if not all) recent kernels load the Skylake FW by symlink, so yes, the symlink needs to stay. The kernel code needs to be fixed anyway. I think there are two possibilities: 1. Fully revert 4aa7fb9c and keep loading the FW by symlink. In this case the check for "required_min_version" would be restored, instead of checking "required_version". 2. Fully restore the behavior introduced by 4aa7fb9c, including the version pinning, and load the FW by direct name. #2 would mean that the firmware needs to stay forever in linux-firmware.git. The current behavior "i915/skl_dmc_ver1.bin is too new, go away" does not make sense, though. Especially if the same FW loaded just fine on *older* kernels. But surely the actual developers have the last word on this.</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>