Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bryan Brattlof via buildroot <buildroot@buildroot.org>
Cc: "Vincent Stehlé" <vincent.stehle@arm.com>,
	"Marleen Vos" <marleen.vos@mind.be>, "Bryan Brattlof" <bb@ti.com>,
	"Sergey Matyukevich" <geomatsi@gmail.com>,
	"Romain Naour" <romain.naour@smile.fr>,
	"Xuanhao Shi" <X15000177@gmail.com>,
	"Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
	"Ariel D'Alessandro" <ariel@vanguardiasur.com.ar>,
	"Romain Naour" <romain.naour@gmail.com>,
	"Michael Trimarchi" <michael@amarulasolutions.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	"Anand Gadiyar" <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH 1/3] boot/arm-trusted-firmware: update source to the new mirror
Date: Sat, 3 Aug 2024 23:59:43 +0200	[thread overview]
Message-ID: <20240803235943.226e6d14@windsurf> (raw)
In-Reply-To: <20240722-tfa-src-update-v1-1-e68bba62f146@ti.com>

Hello Bryan,

On Mon, 22 Jul 2024 14:17:37 -0500
Bryan Brattlof via buildroot <buildroot@buildroot.org> wrote:

> Tags are no longer being pused to the old ARM-softwre
> mirror. Let's move to the new mirror at TrustedFirmware-A which
> continues to publish newer tags
> 
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
>  .../fvp-ebbr/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  .../beagleplay/patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash     | 2 +-
>  .../stm32mp157/patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
>  .../am62ax-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash  | 2 +-
>  .../am62x-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  .../am64x-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  boot/arm-trusted-firmware/arm-trusted-firmware.hash                   | 4 ++--
>  boot/arm-trusted-firmware/arm-trusted-firmware.mk                     | 2 +-
>  12 files changed, 13 insertions(+), 13 deletions(-)

I have applied locally, but not yet pushed. My concern is that it's
really annoying that it breaks hashes for all previous versions of
TF-A. This means that all people having existing defconfigs (not the
one in Buildroot) that use
BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE will see their
build fail now. And even for those using the defconfigs in Buildroot,
they will see a hash mismatch message and a redownload.

But I don't really see any other way around that. The issue is
basically that we are not fetching real tarballs, but auto-generated
ones, which are different when fetched from one repo or another.

Should we instead switch to fetching via Git all the time? Should we
switch to using the official Git repo, instead of a Github mirror?

As you can see, I am not 100% sure about this change, even though we
obviously need to change something to be able to use the newer versions
of TF-A...

Best regards,

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

  reply	other threads:[~2024-08-03 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 19:17 [Buildroot] [PATCH 0/3] boot/arm-trusted-firmware: version bump and source update Bryan Brattlof via buildroot
2024-07-22 19:17 ` [Buildroot] [PATCH 1/3] boot/arm-trusted-firmware: update source to the new mirror Bryan Brattlof via buildroot
2024-08-03 21:59   ` Thomas Petazzoni via buildroot [this message]
2024-08-04  0:52     ` Bryan Brattlof via buildroot
2024-07-22 19:17 ` [Buildroot] [PATCH 2/3] boot/arm-trusted-firmware: bump to v2.11 Bryan Brattlof via buildroot
2024-07-22 19:17 ` [Buildroot] [PATCH 3/3] boot/arm-trusted-firmware: bump latest v2.8 version Bryan Brattlof 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=20240803235943.226e6d14@windsurf \
    --to=buildroot@buildroot.org \
    --cc=X15000177@gmail.com \
    --cc=ariel@vanguardiasur.com.ar \
    --cc=bb@ti.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=gadiyar@ti.com \
    --cc=geomatsi@gmail.com \
    --cc=marleen.vos@mind.be \
    --cc=michael@amarulasolutions.com \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vincent.stehle@arm.com \
    --cc=yann.morin.1998@free.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox