From: Andreas Dannenberg via buildroot <buildroot@buildroot.org>
To: Bryan Brattlof <bb@ti.com>
Cc: Xuanhao Shi <X15000177@gmail.com>,
Romain Naour <romain.naour@smile.fr>,
buildroot@buildroot.org,
Etienne Carriere <etienne.carriere@foss.st.com>,
Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH RESEND v2 02/11] boot/uboot: bump to version v2024.04
Date: Mon, 6 May 2024 03:53:15 -0500 [thread overview]
Message-ID: <20240506085315.lb4frefetaffps6i@dasso> (raw)
In-Reply-To: <20240430-optee-update-v2-2-5bdc2f940db1@ti.com>
Hi Bryan,
On Thu, May 02, 2024 at 11:26:52AM -0500, Bryan Brattlof via buildroot wrote:
> Update to the latest tagged release of U-Boot
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> boot/uboot/Config.in | 6 +++---
> boot/uboot/uboot.hash | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/boot/uboot/Config.in b/boot/uboot/Config.in
> index 8d2228dc7dd45..00d3f3bfbbfdd 100644
> --- a/boot/uboot/Config.in
> +++ b/boot/uboot/Config.in
> @@ -41,7 +41,7 @@ choice
> Select the specific U-Boot version you want to use
>
> config BR2_TARGET_UBOOT_LATEST_VERSION
> - bool "2024.01"
> + bool "2024.04"
Similar to your other patch ("boot/optee-os: bump to release v4.2.0")
changing the global default will affect other platforms so there's some
risk for breakage I suppose. Why not keeping those specific changes to
the AM62/AM64 platforms?
--
Andreas Dannenberg
Texas Instruments Inc
>
> config BR2_TARGET_UBOOT_CUSTOM_VERSION
> bool "Custom version"
> @@ -85,7 +85,7 @@ endif
>
> config BR2_TARGET_UBOOT_VERSION
> string
> - default "2024.01" if BR2_TARGET_UBOOT_LATEST_VERSION
> + default "2024.04" if BR2_TARGET_UBOOT_LATEST_VERSION
> default BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE \
> if BR2_TARGET_UBOOT_CUSTOM_VERSION
> default "custom" if BR2_TARGET_UBOOT_CUSTOM_TARBALL
> @@ -291,7 +291,7 @@ config BR2_TARGET_UBOOT_USE_BINMAN
> help
> Use binman tool for generation and signing of boot images.
>
> - https://docs.u-boot.org/en/v2024.01/develop/package/binman.html
> + https://docs.u-boot.org/en/v2024.04/develop/package/binman.html
>
> menu "U-Boot binary format"
>
> diff --git a/boot/uboot/uboot.hash b/boot/uboot/uboot.hash
> index fbe5d215409d2..a8021fb696b1a 100644
> --- a/boot/uboot/uboot.hash
> +++ b/boot/uboot/uboot.hash
> @@ -1,3 +1,3 @@
> # Locally computed:
> -sha256 b99611f1ed237bf3541bdc8434b68c96a6e05967061f992443cb30aabebef5b3 u-boot-2024.01.tar.bz2
> +sha256 18a853fe39fad7ad03a90cc2d4275aeaed6da69735defac3492b80508843dd4a u-boot-2024.04.tar.bz2
> sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 Licenses/gpl-2.0.txt
>
> --
> 2.43.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-06 8:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 16:26 [Buildroot] [PATCH RESEND v2 00/11] update bsp binaries for TI SoCs Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 01/11] boot/optee-os: bump to release v4.2.0 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 02/11] boot/uboot: bump to version v2024.04 Bryan Brattlof via buildroot
2024-05-06 8:53 ` Andreas Dannenberg via buildroot [this message]
2024-05-06 14:45 ` Bryan Brattlof via buildroot
2024-05-06 20:09 ` Thomas Petazzoni via buildroot
2024-05-07 6:17 ` Andreas Dannenberg via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 03/11] boot/ti-k3-r5-loader: " Bryan Brattlof via buildroot
2024-05-06 20:11 ` Thomas Petazzoni via buildroot
2024-05-08 12:04 ` Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 04/11] boot/ti-k3-boot-firmware: bump to version 09.02.00.009 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 05/11] configs/ti_am62x_sk_defconfig: update TFA to v2.10 Bryan Brattlof via buildroot
2024-05-06 20:10 ` Thomas Petazzoni via buildroot
2024-05-08 12:05 ` Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 06/11] configs/ti_am64x_sk_defconfig: " Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 07/11] configs/ti_am62x_sk_defconfig: update U-Boot to v2024.04 Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 08/11] configs/ti_am64x_sk_defconfig: " Bryan Brattlof via buildroot
2024-05-02 16:26 ` [Buildroot] [PATCH RESEND v2 09/11] configs/ti_am62x_sk_defconfig: bump kernel to v6.8.8 Bryan Brattlof via buildroot
2024-05-06 20:11 ` Thomas Petazzoni via buildroot
2024-05-02 16:27 ` [Buildroot] [PATCH RESEND v2 10/11] configs/ti_am64x_sk_defconfig: update " Bryan Brattlof via buildroot
2024-05-02 16:27 ` [Buildroot] [PATCH RESEND v2 11/11] DEVELOPERS: add myself to TI's packages and reference boards Bryan Brattlof via buildroot
2024-05-06 8:48 ` [Buildroot] [PATCH RESEND v2 00/11] update bsp binaries for TI SoCs Andreas Dannenberg via buildroot
2024-05-06 14:42 ` Bryan Brattlof via buildroot
2024-05-06 20:07 ` Thomas Petazzoni via buildroot
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=20240506085315.lb4frefetaffps6i@dasso \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=bb@ti.com \
--cc=dannenberg@ti.com \
--cc=etienne.carriere@foss.st.com \
--cc=gadiyar@ti.com \
--cc=romain.naour@smile.fr \
/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.