public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/bcm283x-firmware] rawhide: firmware 495ed91, dtbs 6.18.33
Date: Fri, 29 May 2026 16:24:34 +0000 [thread overview]
Message-ID: <rpms-bcm283x-firmware-51e1fd6cc345@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bcm283x-firmware
Branch : rawhide
Commit : 51e1fd6cc34506cfb24f8eef06216f91fb4ee5fc
Author : Peter Robinson <pbrobinson@gmail.com>
Date : 2026-05-29T17:22:11+01:00
Stats : +15/-11 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/bcm283x-firmware/c/51e1fd6cc34506cfb24f8eef06216f91fb4ee5fc?branch=rawhide
Log:
firmware 495ed91, dtbs 6.18.33
---
diff --git a/bcm283x-firmware.spec b/bcm283x-firmware.spec
index e55987a..5d0c6cb 100644
--- a/bcm283x-firmware.spec
+++ b/bcm283x-firmware.spec
@@ -5,10 +5,11 @@
# git clone https://github.com/raspberrypi/firmware.git
# cd firmware/boot
# tar cJvf ../bcm283x-firmware-%{gitshort}.tar.xz *bin *dat *elf LICENCE.broadcom COPYING.linux overlays/
-%define gitshort 8fce67a
+%define gitshort 495ed91
+%define dtbver 6.18.33
Name: bcm283x-firmware
-Version: 20260511
+Version: 20260521
Release: 1.%{gitshort}%{?dist}
Summary: Firmware for the Broadcom bcm283x/bcm271x used in the Raspberry Pi
# see LICENSE.broadcom
@@ -17,6 +18,13 @@ SourceLicense: GPL-2.0-only WITH Linux-syscall-note AND LicenseRef-Fedora-Firmwa
License: LicenseRef-Fedora-Firmware
URL: https://github.com/raspberrypi/
+Source0: %{name}-%{gitshort}.tar.xz
+# tar cJvf bcm-dtbs-v<kerver>.tar.xz bcm271*dtb
+Source1: bcm-dtbs-v%{dtbver}.tar.xz
+Source2: config.txt
+Source3: nortc-time.service
+Source4: cma.dtbo
+
ExclusiveArch: aarch64
BuildRequires: efi-filesystem
@@ -28,13 +36,6 @@ Requires: bcm2835-firmware
Requires: bcm2711-firmware
Requires: bcm2712-firmware
-Source0: %{name}-%{gitshort}.tar.xz
-# tar cJvf bcm-dtbs-v<ker-ver>.tar.xz bcm271*dtb
-Source1: bcm-dtbs-v6.18.21.tar.xz
-Source2: config.txt
-Source3: nortc-time.service
-Source4: cma.dtbo
-
%description
Firmware for the Broadcom bcm283x and bcm2711 series of systems on a chip as
@@ -130,6 +131,9 @@ install -p overlays/*.dtbo %{buildroot}%{efi_esp_root}/overlays
%{efi_esp_root}/bcm2712*
%changelog
+* Fri May 29 2026 Peter Robinson <pbrobinson@fedoraproject.org> - 20260521-1.495ed91
+- Update to latest firmware
+
* Wed May 13 2026 Peter Robinson <pbrobinson@fedoraproject.org> - 20260511-1.8fce67a
- Update to latest firmware
- Fix for USB on some RPi4 revs
diff --git a/sources b/sources
index 10532ad..ebeb918 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (bcm283x-firmware-8fce67a.tar.xz) = 383c034b15900386d454bc69f9e147809079f66ea3da5da07a3276009902c2af95a48dc93ad0becf6f6b969e2a770687bff29d21ebb91f10d23e98cca33de455
-SHA512 (bcm-dtbs-v6.18.21.tar.xz) = 802a1f624fd240a880cb0d2272b7fe5ba06cbd4e3dc803a7044bc44652ff4e8da07296ca558563a82d8390f4bb309d9fb98dcf8bcf5fac8a5a1c815c97acd0b5
+SHA512 (bcm283x-firmware-495ed91.tar.xz) = 42fef47b27e1a898b403fcbbb52acfa6ca9f542d64ef17df9cb53570449d08c739684d89ecf39a1824762e21cc057b247293a281e5b01ba55d2a53a04bbc7344
+SHA512 (bcm-dtbs-v6.18.33.tar.xz) = cd39a10c4351b99668a6ed8499bc348787b9372e64a70a6c622e5e5861690c7bd0818e70a5bc653abcda34bc0b958521d61539272ec746cae58b2d18103a10d3
reply other threads:[~2026-05-29 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=rpms-bcm283x-firmware-51e1fd6cc345@fedoraproject.org \
--to=pbrobinson@gmail.com \
--cc=git-commits@fedoraproject.org \
/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