From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@buildroot.org
Cc: Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
Julien Grossholtz <julien.grossholtz@openest.io>,
Martin Bark <martin@barkynet.com>
Subject: [Buildroot] [PATCH/next v1 2/7] package/rpi-firmware: bump version to fa9a006
Date: Thu, 11 Nov 2021 21:04:34 +0100 [thread overview]
Message-ID: <20211111200439.15379-2-ps.report@gmx.net> (raw)
In-Reply-To: <20211111200439.15379-1-ps.report@gmx.net>
Changelog (since ):
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 0ff7a73a37..7cbfd1b249 100644
--- a/package/rpi-firmware/rpi-firmware.hash
+++ b/package/rpi-firmware/rpi-firmware.hash
@@ -1,3 +1,3 @@
# Locally computed
-sha256 80af5efb51677edb7af6746a553dc2d8ad3f532ff44e4b7263f1e12d4bf72ffd rpi-firmware-2ef3800b1b71c0e30c2a61ecad6e007ae96ea342.tar.gz
+sha256 a079a31fc80a23421589edcacef94faa713b12d3e77b92710ae2594c8d549477 rpi-firmware-fa9a00624e7d5d3dcdb297dff132dc32cc2d9a25.tar.gz
sha256 c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b boot/LICENCE.broadcom
diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
index 3a4741a0ff..5e8b0379ba 100644
--- a/package/rpi-firmware/rpi-firmware.mk
+++ b/package/rpi-firmware/rpi-firmware.mk
@@ -4,7 +4,7 @@
#
################################################################################
-RPI_FIRMWARE_VERSION = 2ef3800b1b71c0e30c2a61ecad6e007ae96ea342
+RPI_FIRMWARE_VERSION = fa9a00624e7d5d3dcdb297dff132dc32cc2d9a25
RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
RPI_FIRMWARE_LICENSE = BSD-3-Clause
RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
--
2.33.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-11 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 20:04 [Buildroot] [PATCH/next v1 1/7] configs/raspberrypi*: bump kernel version to 9878a11 (5.10.78) Peter Seiderer
2021-11-11 20:04 ` Peter Seiderer [this message]
2021-11-12 22:13 ` [Buildroot] [PATCH/next v1 2/7] package/rpi-firmware: bump version to fa9a006 Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 3/7] package/rpi-userland: bump version to bab9bf8 Peter Seiderer
2021-11-12 22:14 ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 4/7] package/rpi-bt-firmware: bump version to 3888ba2 Peter Seiderer
2021-11-12 22:18 ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 5/7] package/rpi-wifi-firmware: " Peter Seiderer
2021-11-12 22:18 ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 6/7] board/raspberrypi/readme.txt: add missing dtb files Peter Seiderer
2021-11-12 22:18 ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 7/7] board/raspberrypi: add Raspberry Pi Zero 2 W Peter Seiderer
2021-11-12 22:19 ` Yann E. MORIN
2021-11-12 22:13 ` [Buildroot] [PATCH/next v1 1/7] configs/raspberrypi*: bump kernel version to 9878a11 (5.10.78) Yann E. MORIN
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=20211111200439.15379-2-ps.report@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=julien.grossholtz@openest.io \
--cc=mahyar.koshkouei@gmail.com \
--cc=martin@barkynet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.