Hi!
Seems the commit 0f0aefd733f7 to linux-firmware effectively broke all
of the setups with the old kernels. Firmware name is an ABI (!) and
replacing it like this will definitely break systems with older
kernels. Linux firmware package likely, but unfortunately, should
carry on both versions as long as it's needed. Alternative solution is
to provide the links during installation.
Btw, I haven't seen the driver change for that. Care to provide a
commit ID in upstream?
--
With Best Regards,
Andy Shevchenko
Seems the commit 0f0aefd733f7 to linux-firmware effectively broke all
of the setups with the old kernels. Firmware name is an ABI (!) and
replacing it like this will definitely break systems with older
kernels. Linux firmware package likely, but unfortunately, should
carry on both versions as long as it's needed. Alternative solution is
to provide the links during installation.
It does provide the links using the copy-firmware.sh and the details in WHENCE.
The alternative is to leave firmwares in place with CVEs.
On Mon, Feb 15, 2021 at 8:03 PM Peter Robinson [off-list ref] wrote:
quoted
Seems the commit 0f0aefd733f7 to linux-firmware effectively broke all
of the setups with the old kernels. Firmware name is an ABI (!) and
replacing it like this will definitely break systems with older
kernels. Linux firmware package likely, but unfortunately, should
carry on both versions as long as it's needed. Alternative solution is
to provide the links during installation.
It does provide the links using the copy-firmware.sh and the details in WHENCE.
The alternative is to leave firmwares in place with CVEs.
Good, thanks, I haven't looked into that script.
--
With Best Regards,
Andy Shevchenko