From: Etienne CARRIERE - foss <etienne.carriere@foss.st.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Romain Naour <romain.naour@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions
Date: Wed, 24 Jul 2024 09:57:06 +0000 [thread overview]
Message-ID: <cae4751a34a8439e9e7f38b75ee9cc13@foss.st.com> (raw)
In-Reply-To: <20240723222829.1526e8c3@windsurf>
Hello Thomas,
On Tuesday, July 23, 2024, Thomas Petazzoni wrote:
> On Tue, 23 Jul 2024 18:30:24 +0200
> Etienne Carriere <etienne.carriere@foss.st.com> wrote:
>
> > Bump TF-A to version v2.10 and U-Boot to version v2024.07 for
> > Qemu arm-vexpress/trustzone board config.
> >
> > Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
> > ---
> > configs/qemu_arm_vexpress_tz_defconfig | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Thanks for the patch. However, are you sure you tested it? Indeed this
> defconfig has BR2_DOWNLOAD_FORCE_CHECK_HASHES=y, which means all hashes
> are checked. So when you bump components, it cannot be done without
> updating hashes in board/qemu/patches/. Please note that those hash
> files are shared by all qemu defconfigs. Could you check this?
Sorry, indeed I realize i forgot to re-parse the defconfig after applying the change.
Bad test, my apologies.
It happens that building with these U-Boot / TF-A versions works ok.
No hash failure on U-Boot or TF-A source tree blobs but actually, the source tarball hashes for these versions are defined in relative boot/xxx/xxx.hash.
That said, booting this platform with U-Boot 2024.07 fails. I did not expect that.
I think I'll upgrade at least to TF-A v2.10 (there's an LTS on that tag) and will postpone U-Boot version bump to later.
Regards,
Etienne
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-24 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 16:30 [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions Etienne Carriere
2024-07-23 16:30 ` [Buildroot] [PATCH v2 2/2] board/qemu/arm-vexpress-tz: fix typos in readme file Etienne Carriere
2024-07-23 20:29 ` Thomas Petazzoni via buildroot
2024-08-31 16:56 ` Peter Korsgaard
2024-07-23 20:28 ` [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions Thomas Petazzoni via buildroot
2024-07-24 9:57 ` Etienne CARRIERE - foss [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=cae4751a34a8439e9e7f38b75ee9cc13@foss.st.com \
--to=etienne.carriere@foss.st.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.