From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] linux-firmware: Version bump. 20220708 -> 20220913
Date: Thu, 22 Sep 2022 15:43:17 +0200 [thread overview]
Message-ID: <20220922134317.3650514-1-christian.melki@t2data.com> (raw)
The usual churn. GPU and radio devices.
AMD GC firmwares probably stepped for coming Ryzen 7000 based APUs.
* Add license for cirrus.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/linux-firmware.make | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/rules/linux-firmware.make b/rules/linux-firmware.make
index 9a8f1db47..287bfd63e 100644
--- a/rules/linux-firmware.make
+++ b/rules/linux-firmware.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LINUX_FIRMWARE) += linux-firmware
#
# Paths and names
#
-LINUX_FIRMWARE_VERSION := 20220708
-LINUX_FIRMWARE_MD5 := a4389b0cfb921ad5209d8ddbed7f7548
+LINUX_FIRMWARE_VERSION := 20220913
+LINUX_FIRMWARE_MD5 := 1ea1f09e040b8c86d4bc4a4e41acffc5
LINUX_FIRMWARE := linux-firmware-$(LINUX_FIRMWARE_VERSION)
LINUX_FIRMWARE_SUFFIX := tar.gz
LINUX_FIRMWARE_URL := $(call ptx/mirror, KERNEL, kernel/firmware/$(LINUX_FIRMWARE).$(LINUX_FIRMWARE_SUFFIX))
@@ -86,6 +86,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
file://LICENSE.ice;md5=742ab4850f2670792940e6d15c974b2f \
file://LICENCE.myri10ge_firmware;md5=42e32fb89f6b959ca222e25ac8df8fed \
file://LICENCE.Netronome;md5=4add08f2577086d44447996503cddf5f \
+ file://LICENSE.cirrus;md5=bb18d943382abf8e8232a9407bfdafe0 \
file://LICENCE.phanfw;md5=954dcec0e051f9409812b561ea743bfa \
file://LICENCE.ca0132;md5=209b33e66ee5be0461f13d31da392198 \
file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
--
2.34.1
next reply other threads:[~2022-09-22 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:43 Christian Melki [this message]
2022-09-28 14:28 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20220922134317.3650514-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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