All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vic B via U-Boot <u-boot@lists.u-boot-project.org>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	u-boot@lists.u-boot-project.org
Subject: Re: RK3399 TF-A hash verification failure for atf-3
Date: Fri, 31 Jul 2026 01:01:33 +0200	[thread overview]
Message-ID: <amvXzWK9xzUEFIxV@localhost> (raw)
In-Reply-To: <CALeDE9N1GUu7z2vL4SG+JNyA32Ro207P1QQCPUuxz6QycJ-dGA@mail.gmail.com>

On Thu, Jul 30, 2026 at 02:59:05PM +0100, Peter Robinson wrote:
> > Debian toolchain issue, reported to TF-A last year, see
> > https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/36981/comments/877be809_5abf10d8.
> > We wanted to rely on Debian upgrading at some point their TF-A, hitting
> > the same issue and working on it but it seems they are stuck on
> > lts-v2.12.1 (which is slightly concerning considering we're at
> > lts-v2.12.12 already) so this hasn't happened yet. I'm building on
> > Fedora and my company's CI has lts-v2.12 pinned to avoid this issue, so
> > I'm not going to be chasing this myself. Can you try to work this out
> > with Debian maybe? You're not the first, not the last I suspect either.
> 
> The distro team got to the bottom of the problem, it's an issue with
> the TF-A linker [1] not getting that CPU errata may well be enabled by
> default in a compiler options. The patch I think should apply to most
> branches of TF-A.
> 
> [1] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/53010

Works like a charm, thanks!

Vic

      reply	other threads:[~2026-07-30 23:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 16:03 RK3399 TF-A hash verification failure for atf-3 Vic B
2026-07-22 16:23 ` Peter Robinson via U-Boot
2026-07-24 10:57   ` Vic B via U-Boot
2026-07-22 17:12 ` Quentin Schulz via U-Boot
2026-07-22 22:29   ` Peter Robinson
2026-07-24 12:38   ` Vic B via U-Boot
2026-07-24 12:55     ` Quentin Schulz
2026-07-26 11:46       ` Vic B via U-Boot
2026-07-27 12:12         ` Peter Robinson
2026-07-27 20:15           ` Vic B via U-Boot
2026-07-30 13:59   ` Peter Robinson
2026-07-30 23:01     ` Vic B via U-Boot [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=amvXzWK9xzUEFIxV@localhost \
    --to=u-boot@lists.u-boot-project.org \
    --cc=pbrobinson@gmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=u-boot@vicb.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.