[Buildroot] [PATCH v1 2/3] package/rpi-firmware: bump version to 62a0d75

Peter Seiderer ps.report at gmx.net
Wed Jan 15 20:55:10 UTC 2020


Hello Martin,

On Tue, 14 Jan 2020 19:44:44 +0000, Martin Bark <martin at barkynet.com> wrote:

> Peter,
>
> On Tue, 14 Jan 2020 at 17:29, Peter Seiderer <ps.report at gmx.net> wrote:
> >
> > Hello Yann,
> >
> > On Tue, 14 Jan 2020 17:36:53 +0100, "Yann E. MORIN" <yann.morin.1998 at free.fr> wrote:
> >
> > > Peter, All,
> > >
> > > On 2020-01-14 10:42 +0100, Peter Seiderer spake thusly:
> > > > Signed-off-by: Peter Seiderer <ps.report at gmx.net>
> > > > ---
> > > >  package/rpi-firmware/rpi-firmware.hash | 2 +-
> > > >  package/rpi-firmware/rpi-firmware.mk   | 2 +-
> > > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
> > > > index 63d8ac50a0..b5bb4d9f37 100644
> > > > --- a/package/rpi-firmware/rpi-firmware.hash
> > > > +++ b/package/rpi-firmware/rpi-firmware.hash
> > > > @@ -1,3 +1,3 @@
> > > >  # Locally computed
> > > > -sha256 b3c5c9d3cda1f77caf317b8d1f0496cd7ca791ddaeec8207a5a1940111483509 rpi-firmware-1.20190925.tar.gz
> > > > +sha256 088d094618924a90f65bb511808bbeb921e0769c878fa7baa9626954206f61a2 rpi-firmware-62a0d75b67484cb306a2a6f8fa954d9644868169.tar.gz
> > > >  sha256 ba76edfc10a248166d965b8eaf320771c44f4f432d4fce2fd31fd272e7038add boot/LICENCE.broadcom
> > > > diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> > > > index ee59ee2f26..b320e11233 100644
> > > > --- a/package/rpi-firmware/rpi-firmware.mk
> > > > +++ b/package/rpi-firmware/rpi-firmware.mk
> > > > @@ -4,7 +4,7 @@
> > > >  #
> > > >  ################################################################################
> > > >
> > > > -RPI_FIRMWARE_VERSION = 1.20190925
> > > > +RPI_FIRMWARE_VERSION = 62a0d75b67484cb306a2a6f8fa954d9644868169
> > >
> > > This goes from a tag to a sha1. Why do we need to do so? This should be
> > > explained in the commit log.
> >
> > No new tag since 1.20190925...., and tags seems to be the exception for
> > buildroot (two times tags, numerous ones sha1), and we want to keep
> > rpi-firmware up to the same as the rpi linux-kernel (see e.g.
> > 'kernel: Bump to 4.19.95' [1])...
>
> The tags match the release of the kernel in raspbian.  So the current
> kernel used in raspbian is 1.20190925, no new one has been released
> yet.  I think we should stick with released kernels.

Trade off between 'offical' and up-to-date, I am in favour for the
up-to-date ;-), 4.19.75 vs. 4.19.93 and as mentioned already in [2]
'...tags seems to be the exception for buildroot (two times tags,
numerous ones sha1)...'

Regards,
Peter

[2] http://lists.busybox.net/pipermail/buildroot/2020-January/271589.html

>
> Thanks
>
> Martin
>
> >
> > Regards,
> > Peter
> >
> > [1] https://github.com/raspberrypi/firmware/commit/d5b8d8d7cce3f3eecb24c20a55cc50a48e3d5f4e
> >
> > >
> > > Regards,
> > > Yann E. MORIN.
> > >
> > > >  RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
> > > >  RPI_FIRMWARE_LICENSE = BSD-3-Clause
> > > >  RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
> > > > --
> > > > 2.24.1
> > > >
> > > > _______________________________________________
> > > > buildroot mailing list
> > > > buildroot at busybox.net
> > > > http://lists.busybox.net/mailman/listinfo/buildroot
> > >
> >




More information about the buildroot mailing list