From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/arm-trusted-firmware: bump to version 2.5
Date: Fri, 21 May 2021 11:45:42 +0200 [thread overview]
Message-ID: <20210521094542.GI3208066@scaer> (raw)
In-Reply-To: <20210521091332.28982-1-heiko.thiery@gmail.com>
Heiko, All,
On 2021-05-21 11:13 +0200, Heiko Thiery spake thusly:
> Release notes:
> https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-5
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
> boot/arm-trusted-firmware/Config.in | 4 ++--
> boot/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/boot/arm-trusted-firmware/Config.in b/boot/arm-trusted-firmware/Config.in
> index c06294040e..feef6eb50c 100644
> --- a/boot/arm-trusted-firmware/Config.in
> +++ b/boot/arm-trusted-firmware/Config.in
> @@ -15,7 +15,7 @@ choice
> Select the specific ATF version you want to use
>
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_VERSION
> - bool "v2.4"
> + bool "v2.5"
I noticed that qemu_aarch64_sbsa_defconfig was using an unpinned version
of ATF, so bumping ATF would cause that defconfig to use a newer version
it was not tested against. So I've pinned qemu_aarch64_sbsa_defconfig to
use 2.4 and applied to next, thanks.
Regards,
Yann E. MORIN.
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION
> bool "Custom version"
> @@ -43,7 +43,7 @@ config BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE
>
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE_VERSION
> string
> - default "v2.4" if BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_VERSION
> + default "v2.5" if BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_VERSION
> default "custom" if BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL
> default BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION \
> if BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT
> diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.hash b/boot/arm-trusted-firmware/arm-trusted-firmware.hash
> index 970613f38d..1ab50a9e28 100644
> --- a/boot/arm-trusted-firmware/arm-trusted-firmware.hash
> +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 4bfda9fdbe5022f2e88ad3344165f7d38a8ae4a0e2d91d44d9a1603425cc642d arm-trusted-firmware-v2.4.tar.gz
> +sha256 d12a824afcc5cb90d005f9820f3274f1319cef1bb282e40a6a190b75900206d3 arm-trusted-firmware-v2.5.tar.gz
> sha256 487795b8023df866259fa159bab94706b747fb0d623b7913f1c4955c0ab5f164 license.rst
> --
> 2.30.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2021-05-21 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 9:13 [Buildroot] [PATCH] boot/arm-trusted-firmware: bump to version 2.5 Heiko Thiery
2021-05-21 9:45 ` Yann E. MORIN [this message]
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=20210521094542.GI3208066@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.