Bug#735092: flash-kernel: add Raspberry Pi support
On Sun, Jan 12, 2014 at 08:40:29PM +0000, Ben Hutchings wrote:
> On Sun, 2014-01-12 at 21:16 +0100, Karsten Merker wrote:
> > Having the vfat boot partition as /boot is the standard way in
> > Raspbian (Debian/armhf rebuild for the Pi/armv6, "official" OS
> > distribution for the Pi) and is described this way in all user
> > documentation for the Pi. This is also expected by other
> > software, in particular the firmware update mechanism, which
> > expects the firmware image to be at
> > /boot/bootcode.bin, as well as by the Raspberry Pi foundation's
> > kernel updates (which do not come as a Debian kernel package).
>
> Then I'm not sure what the point of this change is. Unpackaged kernel
> updates, aside from being generally a Bad Thing, presumably won't
> automatically call flash-kernel.
My intention was a) to make life easier for users who use kernel
packages built from the RPi kernel git and other unofficial
repositories and b) offer infrastructure which might some day be
used for the official kernel releases as well.
> > - The firmware update mechanism would have to be changed. This is
> > outside the scope of Debian and as installing firmware updates
> > is something that happens rather frequently on the Pi, that
> > must work without problems.
>
> ln -s boot/bootcode.bin /boot/bootcode.bin ?
I am at the moment unsure whether the current update mechanism
works properly with a symlink; I'll test that.
> There is obvious precedent for systems with firmware that boots from a
> VFAT partition. On EFI systems, starting with ia64 around 10 years ago,
> GNU/Linux usually mounts the firmware-supported boot partition at
> /boot/efi rather than /boot.
I'll talk to Peter Green (one of the people behind Raspbian)
about the issue.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: