[Pkg-raspi-maintainers] Bug#948712: Returned mail: see transcript for details
Elliott Mitchell
ehem+debian at m5p.com
Tue Nov 24 03:36:50 GMT 2020
reopen 948712
quit
There should be a rather obvious use case where absent /boot/firmware is
quite appropriate. For someone needing a copy of the firmware, but using
other tools to build the boot area.
Notably one might use raspi-firmware to retrieve start*.elf/fixup*.dat.
Then add u-boot-rpi for second stage bootloader. Next grub-efi-arm* for
third stage. Lastly flash-kernel to glue all the pieces together.
Not one of these requires the existance of /boot/firmware. In fact, not
one of these needs the installation of dosfstools.
Perhaps the raspi-firmware package should be split into pieces so as to
allow merely installing the actually required portions?
(raspi-firmware-bin which depends upon: raspi1-firmware-bin,
raspi2-firmware-bin, raspi3-firmware-bin, and raspi4-firmware-bin?)
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg at m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
More information about the Pkg-raspi-maintainers
mailing list