From: Jon Mason <jon.mason@arm.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH] arm/trusted-firmware-a: update to lts-2.10.4
Date: Wed, 1 May 2024 08:31:33 -0400 [thread overview]
Message-ID: <20240501123133.62536-1-jon.mason@arm.com> (raw)
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
.../{fiptool-native_2.10.3.bb => fiptool-native_2.10.4.bb} | 4 ++--
...sted-firmware-a_2.10.3.bb => trusted-firmware-a_2.10.4.bb} | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta-arm/recipes-bsp/trusted-firmware-a/{fiptool-native_2.10.3.bb => fiptool-native_2.10.4.bb} (92%)
rename meta-arm/recipes-bsp/trusted-firmware-a/{trusted-firmware-a_2.10.3.bb => trusted-firmware-a_2.10.4.bb} (86%)
diff --git a/meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.3.bb b/meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.4.bb
similarity index 92%
rename from meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.3.bb
rename to meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.4.bb
index 5ba8d48cb499..9072dca50a50 100644
--- a/meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.3.bb
+++ b/meta-arm/recipes-bsp/trusted-firmware-a/fiptool-native_2.10.4.bb
@@ -9,8 +9,8 @@ SRC_URI_TRUSTED_FIRMWARE_A ?= "git://git.trustedfirmware.org/TF-A/trusted-firmwa
SRC_URI = "${SRC_URI_TRUSTED_FIRMWARE_A};destsuffix=fiptool-${PV};branch=${SRCBRANCH}"
LIC_FILES_CHKSUM = "file://docs/license.rst;md5=b2c740efedc159745b9b31f88ff03dde"
-# Use fiptool from TF-A v2.10.3
-SRCREV = "0f915309c3821ce6f78f8451e5a6178d0cf07611"
+# Use fiptool from TF-A v2.10.4
+SRCREV = "569e16caad976a0684147da1ecc6333fd9b7f813"
SRCBRANCH = "lts-v2.10"
DEPENDS += "openssl-native"
diff --git a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.3.bb b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.4.bb
similarity index 86%
rename from meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.3.bb
rename to meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.4.bb
index b30ac7252d77..21598c822915 100644
--- a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.3.bb
+++ b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.4.bb
@@ -1,7 +1,7 @@
require recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
-# TF-A v2.10.3
-SRCREV_tfa = "0f915309c3821ce6f78f8451e5a6178d0cf07611"
+# TF-A v2.10.4
+SRCREV_tfa = "569e16caad976a0684147da1ecc6333fd9b7f813"
SRCBRANCH = "lts-v2.10"
LIC_FILES_CHKSUM += "file://docs/license.rst;md5=b2c740efedc159745b9b31f88ff03dde"
--
2.39.3 (Apple Git-146)
next reply other threads:[~2024-05-01 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 12:31 Jon Mason [this message]
2024-05-02 14:13 ` [PATCH] arm/trusted-firmware-a: update to lts-2.10.4 Jon Mason
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=20240501123133.62536-1-jon.mason@arm.com \
--to=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).