From: Jon Mason <jon.mason@arm.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH 1/2] arm/scp-firmware: update to 2.16.0
Date: Fri, 18 Apr 2025 09:12:00 -0400 [thread overview]
Message-ID: <20250418131201.95204-1-jon.mason@arm.com> (raw)
Update SCP to the latest tagged version, and update the related patch to
the new location of the relevant files.
For a comparison of the changes, please go to
https://git.gitlab.arm.com/firmware/SCP-firmware/-/compare/v2.15.0...v2.16.0
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
.../{scp-firmware_2.15.0.bb => scp-firmware_2.16.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-arm/recipes-bsp/scp-firmware/{scp-firmware_2.15.0.bb => scp-firmware_2.16.0.bb} (98%)
diff --git a/meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.15.0.bb b/meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.16.0.bb
similarity index 98%
rename from meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.15.0.bb
rename to meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.16.0.bb
index b305234347f2..66cf4e44962f 100644
--- a/meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.15.0.bb
+++ b/meta-arm/recipes-bsp/scp-firmware/scp-firmware_2.16.0.bb
@@ -12,7 +12,7 @@ SRC_URI = "${SRC_URI_SCP_FIRMWARE};branch=${SRCBRANCH} \
"
SRCBRANCH = "main"
-SRCREV = "25681b34bdc838b7231e0056e3ef5164e8005382"
+SRCREV = "190e938c2da3631b4834a90448516423099c79f7"
PROVIDES += "virtual/control-processor-firmware"
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-04-18 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 13:12 Jon Mason [this message]
2025-04-18 13:12 ` [PATCH 2/2] arm/python3-pydevicetree: update to 0.0.13 Jon Mason
2025-04-19 3:15 ` [PATCH 1/2] arm/scp-firmware: update to 2.16.0 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=20250418131201.95204-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 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.