[PATCH v2 35/35] bloblist: Allow using a different bloblist address
Tom Rini
trini at konsulko.com
Mon Feb 10 15:33:12 CET 2025
On Sun, Feb 09, 2025 at 02:14:56PM -0700, Simon Glass wrote:
> Where the bloblist is located in internal memory and TF-A's BL31 blob
> removes access to this memory, the best option seems to be to relocate
> the bloblist just before running TF-A.
>
> We can do the relocation in board-specific code, but need an option to
> pick up the correct address within U-Boot proper.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
>
> Changes in v2:
> - Move the actual relocation code to a previous board-specific patch
>
> common/Kconfig | 20 ++++++++++++++++++++
> common/bloblist.c | 15 ++++++++++++++-
> 2 files changed, 34 insertions(+), 1 deletion(-)
I'm going to NAK this whole concept. The whole nightmare thread about
these platforms comes from using a fixed address. We need to pass in a
bloblist or see that one is not passed to us, via register. And then use
that mechanism to pass the bloblist to the next phase. When we don't
have a bloblist passed to us, we allocate one, and not at a fixed
location.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20250210/d56de269/attachment.sig>
More information about the U-Boot
mailing list