> I'm still inclined to be conservative about this; loading of drivers
> can be finicky, and even a change which is demonstrably correct can
> break working systems in the field.
Well, it's your call. It's not a big deal for me - I can happily live
with my old initramfs-hook for as long as it takes. :-)
Anyway, done testing now. I stuffed the firmware image in the expected
place at /lib/firmware/`uname -r` and it was copied to the initramfs,
and loaded correctly during bootup. So the fix is good.
* Matt Zimmerman
> I'm still inclined to be conservative about this; loading of drivers
> can be finicky, and even a change which is demonstrably correct can
> break working systems in the field.
Well, it's your call. It's not a big deal for me - I can happily live
with my old initramfs-hook for as long as it takes. :-)
Anyway, done testing now. I stuffed the firmware image in the expected `uname -r` and it was copied to the initramfs,
place at /lib/firmware/
and loaded correctly during bootup. So the fix is good.
Regards
--
Tore Anderson