Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] package/rpi-firmware: bump version to 62a0d75
Date: Wed, 15 Jan 2020 21:55:10 +0100	[thread overview]
Message-ID: <20200115215510.5f6e4f67@gmx.net> (raw)
In-Reply-To: <CAFGQKxfZj5ct49TttwOqwzq6r3WYVbCOcKD06qPmS9dEqtaTeg@mail.gmail.com>

Hello Martin,

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

> Peter,
>
> On Tue, 14 Jan 2020 at 17:29, Peter Seiderer <ps.report@gmx.net> wrote:
> >
> > Hello Yann,
> >
> > On Tue, 14 Jan 2020 17:36:53 +0100, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> >
> > > Peter, All,
> > >
> > > On 2020-01-14 10:42 +0100, Peter Seiderer spake thusly:
> > > > Signed-off-by: Peter Seiderer <ps.report@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
> > >
> >

  reply	other threads:[~2020-01-15 20:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  9:42 [Buildroot] [PATCH v1 1/3] configs/raspberrypi*: bump kernel version to 301ec88 Peter Seiderer
2020-01-14  9:42 ` [Buildroot] [PATCH v1 2/3] package/rpi-firmware: bump version to 62a0d75 Peter Seiderer
2020-01-14 16:36   ` Yann E. MORIN
2020-01-14 17:29     ` Peter Seiderer
2020-01-14 19:44       ` Martin Bark
2020-01-15 20:55         ` Peter Seiderer [this message]
2020-01-14  9:42 ` [Buildroot] [PATCH v1 3/3] package/rpi-userland: bump version to 42ec119 Peter Seiderer
2020-01-14 12:45   ` daggs
2020-01-14 14:27     ` Peter Seiderer
2020-01-14 16:32       ` Yann E. MORIN
2020-01-14 17:19       ` Peter Seiderer
2020-01-14 20:20         ` Thomas Petazzoni
2020-01-14 21:17         ` daggs
2020-01-15 20:57           ` Peter Seiderer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200115215510.5f6e4f67@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox