All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Henningsen <stephan@asklandd.dk>
To: buildroot@buildroot.org
Subject: [Buildroot] linux-firmware-bump-to-20221109.patch
Date: Thu, 08 Dec 2022 22:10:25 +0100	[thread overview]
Message-ID: <D5CLMR.W52FYUR7ME313@asklandd.dk> (raw)

linux-firmware.mk: bump to release 20221109
linux-firmware.hash: add hash of bumped tarball, remove hash of deleted 
files

Signed-off-by: Stephan Henningsen <stephan+buildroot@asklandd.dk>

diff -purN linux-firmware.orig/linux-firmware.hash 
linux-firmware/linux-firmware.hash
--- linux-firmware.orig/linux-firmware.hash 2022-12-08 
21:35:15.051696882 +0100
+++ linux-firmware/linux-firmware.hash 2022-12-01 00:17:16.257440762 
+0100
@@ -1,5 +1,5 @@
 # From 
https://mirrors.edge.kernel.org/pub/linux/kernel/firmware/sha256sums.asc
-sha256 
e9d174af729511c8cccb60ec4e0b223b3c44b67d813b42d1ab9813acfa667fa5 
linux-firmware-20221012.tar.xz
+sha256 
c0ddffbbcf30f2e015bddd5c6d3ce1f13976b906aceabda4a57e3c41a3190701 
linux-firmware-20221109.tar.xz

 # Hash for license files
 sha256 
8116433f4004fc0c24d72b3d9e497808b724aa0e5e1cd63fc1bf66b715b1e2e9 
LICENCE.Abilis
@@ -14,11 +14,9 @@ sha256 a5777f9e80aca0603b0648454de99616
 sha256 
ae0db6cc4db33941148df0f67de53e76a77b1b5a46b3165edb7040aa2750015f 
LICENCE.cypress
 sha256 
60fbc9cccb455e1a3306c97db942d6f24fa93664be61d54c497637e6d0e2ae83 
LICENCE.fw_sst_0f28
 sha256 
5181b0b51efc79d5acb2c9bb92042878fdbad97a92114d4ab5e32e2b5b52fce4 
LICENCE.ibt_firmware
-sha256 
8c45a83562a69f7ac4207e4cb5c0063af2e545791b3947bc81dc82305481c15c 
LICENSE.ice_enhanced
 sha256 
0e0c11073ba3c832097da38e0905da36b8a3526f219407977b13b71c6675be7d 
LICENCE.it913x
 sha256 
16d5040c7cf851fc693b7542e20870935b99802533ea1bfd231c377a2305e5c5 
LICENCE.iwlwifi_firmware
 sha256 
0fc67bd715b3395f3f2af464781910e9e69c4ba23da304352229b42dc9e986c3 
LICENCE.microchip
-sha256 
59ae206c89108905ebdc9ad4c9336526bd2c0d50fbf988c21e8c2a82719d42a4 
LICENCE.moxa
 sha256 
2051d5bf0755a0668f8c3d9a0d1c41d4b8cc411aba70f720fda71ae9e3b4d25c 
LICENCE.qat_firmware
 sha256 
4071a11d878dbc0ac6d9e71203d03b151638f9d7a8bc47a54c3cb964100d5822 
LICENCE.qla2xxx
 sha256 
d7bec70668ddd4aae8fb4aa32870e54b49fcdb0b9b007aa9f54b53a1ac7461bd 
LICENCE.ralink-firmware.txt
@@ -35,6 +33,7 @@ sha256 8542aeabf2761935122d693561e16766
 sha256 
be904cd28cb292b80cdb6cf412ab0d9159d431671e987ad433c1f62e0988a9bc 
LICENSE.qcom
 sha256 
fc6223d4bfe9f2f9e2eddc44b9fe5721d0caf49f01cb08d602906add686d8c6f 
LICENSE.radeon
 sha256 
2bdd2e716f05d9737d3f9a20f9a3a3c0caee0e866100ddb0673f1178e42f92b9 
LICENSE.sdma_firmware
-sha256 
6857749e23d6a2853e5d33f6d6012a60d5baa2b4d51b5f8c6799d00d68733841 WHENCE
+sha256 
75afdb5d45a21ff95ff7aa82d67bc42a83830f2def98ea937c01d6e7603d76f9 WHENCE
 sha256 
fa43e1b9a13b341a07adca9dbe73d0f9072d7966fdfe811c01f0dd2872d7309a 
qcom/NOTICE.txt
 sha256 
bef9c828e84f21e7835b4de7daf954a327e1ff777871b58e116039b684c0d604 
LICENCE.e100
+
diff -purN linux-firmware.orig/linux-firmware.mk 
linux-firmware/linux-firmware.mk
--- linux-firmware.orig/linux-firmware.mk 2022-12-08 21:35:15.051696882 
+0100
+++ linux-firmware/linux-firmware.mk 2022-12-08 21:38:27.868382561 +0100
@@ -4,7 +4,7 @@
 #
 
################################################################################

-LINUX_FIRMWARE_VERSION = 20221012
+LINUX_FIRMWARE_VERSION = 20221109
 LINUX_FIRMWARE_SOURCE = linux-firmware-$(LINUX_FIRMWARE_VERSION).tar.xz
 LINUX_FIRMWARE_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/firmware
 LINUX_FIRMWARE_INSTALL_IMAGES = YES



_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-12-08 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 21:10 Stephan Henningsen [this message]
2022-12-11 10:31 ` [Buildroot] linux-firmware-bump-to-20221109.patch Thomas Petazzoni via buildroot

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=D5CLMR.W52FYUR7ME313@asklandd.dk \
    --to=stephan@asklandd.dk \
    --cc=buildroot@buildroot.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 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.