From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version
Date: Thu, 15 Mar 2018 20:28:56 +0100 [thread overview]
Message-ID: <20180315202856.39b87c81@gmx.net> (raw)
In-Reply-To: <1521120291-15781-1-git-send-email-martin@barkynet.com>
Hello Martin,
On Thu, 15 Mar 2018 13:24:48 +0000, Martin Bark <martin@barkynet.com> wrote:
> Signed-off-by: Martin Bark <martin@barkynet.com>
> ---
> 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 833a7fb..0e09ff5 100644
> --- a/package/rpi-firmware/rpi-firmware.hash
> +++ b/package/rpi-firmware/rpi-firmware.hash
> @@ -1,2 +1,2 @@
> # Locally computed
> -sha256 0451e1a843bf02df81126a1625d9a15dfdf19dcb2f9e95b0613a63e59fd31ca8 rpi-firmware-2067241bc7cdf238fdeab7f5a3c22faa57dd5617.tar.gz
> +sha256 8fe5ebe14cc900f67242cab0c1c9f8e29bd10369ccbdfc7d004c294a96bad975 rpi-firmware-086a8488de0f485e8879ac14ff505ff1d922eeed.tar.gz
> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> index 22eaaa2..1ebdd96 100644
> --- a/package/rpi-firmware/rpi-firmware.mk
> +++ b/package/rpi-firmware/rpi-firmware.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -RPI_FIRMWARE_VERSION = 2067241bc7cdf238fdeab7f5a3c22faa57dd5617
> +RPI_FIRMWARE_VERSION = 086a8488de0f485e8879ac14ff505ff1d922eeed
This commit (and some more before) have a reference to kernel branch 4.14.x, this one
with subject 'kernel: Bump to 4.14.26'...
The last commit referencing kernel branch 4.9.x is b1a7f4aea6cbd380319c2849ecc5988f9a4dba70
'kernel: Bump to 4.9.80', for consistence your should bump the firmware version to this
commit (or bump the kernel versions to the latest from the 4.14.x branch)...
Regards,
Peter
> RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
> RPI_FIRMWARE_LICENSE = BSD-3-Clause
> RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
next prev parent reply other threads:[~2018-03-15 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 13:24 [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 2/4] configs/raspberrypi*: bump kernel version Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 3/4] board/raspberrypi: add support for rpi3 b+ Martin Bark
2018-03-15 13:33 ` Baruch Siach
2018-03-15 14:07 ` Martin Bark
2018-03-15 13:24 ` [Buildroot] [PATCH 4/4] package/rpi-firmware: improve installation of dtb files Martin Bark
2018-03-15 19:40 ` Peter Seiderer
2018-03-15 19:58 ` Martin Bark
2018-03-15 21:59 ` Yann E. MORIN
2018-03-15 22:40 ` Martin Bark
2018-03-16 9:32 ` Jens Maus
2018-03-16 10:52 ` Martin Bark
2018-03-16 13:07 ` Peter Korsgaard
2018-03-16 13:12 ` Jens Maus
2018-03-16 18:08 ` Martin Bark
2018-03-15 19:28 ` Peter Seiderer [this message]
2018-03-15 20:23 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Martin Bark
-- strict thread matches above, loose matches on Subject: below --
2013-09-04 21:35 [Buildroot] [pull request] Pull request for branch yem/misc-updates Yann E. MORIN
2013-09-04 21:35 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Yann E. MORIN
2013-09-05 13:42 ` Peter Korsgaard
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=20180315202856.39b87c81@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