mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] linux-firmware: Version bump. 20221214 -> 20230117
Date: Thu, 19 Jan 2023 09:44:14 +0100	[thread overview]
Message-ID: <20230119084414.998429-1-christian.melki@t2data.com> (raw)

Mostly AMDGPU firmware and radio stuff.

* License file for AMDGPU had license year change.
* Added qualcomm yamato (the old adreno A20x) license.

Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
 rules/linux-firmware.make | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/rules/linux-firmware.make b/rules/linux-firmware.make
index 1a1cdaa16..6bb6e8c7b 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	:= 20221214
-LINUX_FIRMWARE_MD5	:= 93ba47547b9c2e538d11de95405939b2
+LINUX_FIRMWARE_VERSION	:= 20230117
+LINUX_FIRMWARE_MD5	:= 0e8cabf84ff6c034113df5816e6d2414
 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))
@@ -62,7 +62,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
 	file://LICENCE.ralink_a_mediatek_company_firmware;md5=728f1a85fd53fd67fa8d7afb080bc435 \
 	file://LICENCE.ti-keystone;md5=3a86335d32864b0bef996bee26cc0f2c \
 	file://LICENSE.amd-sev;md5=e750538791a8be0b7249c579edefb035 \
-	file://LICENSE.amdgpu;md5=44c1166d052226cb2d6c8d7400090203 \
+	file://LICENSE.amdgpu;md5=a2589a05ea5b6bd2b7f4f623c7e7a649 \
 	file://LICENSE.nxp;md5=cca321ca1524d6a1e4fed87486cd82dc \
 	file://LICENCE.agere;md5=af0133de6b4a9b2522defd5f188afd31 \
 	file://LICENCE.siano;md5=4556c1bf830067f12ca151ad953ec2a5 \
@@ -82,6 +82,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
 	file://LICENSE.Lontium;md5=4ec8dc582ff7295f39e2ca6a7b0be2b6 \
 	file://LICENCE.rockchip;md5=5fd70190c5ed39734baceada8ecced26 \
 	file://LICENCE.it913x;md5=1fbf727bfb6a949810c4dbfa7e6ce4f8 \
+	file://LICENSE.qcom_yamato;md5=d0de0eeccaf1843a850bf7a6777eec5c \
 	file://LICENCE.OLPC;md5=5b917f9d8c061991be4f6f5f108719cd \
 	file://LICENCE.qat_firmware;md5=9e7d8bea77612d7cc7d9e9b54b623062 \
 	file://LICENSE.ice;md5=742ab4850f2670792940e6d15c974b2f \
-- 
2.34.1




             reply	other threads:[~2023-01-19  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  8:44 Christian Melki [this message]
2023-02-08 11:49 ` [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=20230119084414.998429-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