From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Simon Glass <sjg@chromium.org>
Cc: trini@konsulko.com, u-boot@lists.denx.de, monstr@monstr.eu,
hl@rock-chips.com, jeffy.chen@rock-chips.com,
kever.yang@rock-chips.com, uboot-imx@nxp.com, marek.behun@nic.cz,
yamada.masahiro@socionext.com
Subject: Re: [PATCH v2 2/2] Makefile: Don't allow new boards with SPL_FIT_GENERATOR
Date: Tue, 1 Feb 2022 17:08:14 +0100 (CET) [thread overview]
Message-ID: <d3cbf782e80b057d@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAPnjgZ2DbWqB5jZFJF4-R1_LS3Y_FPuVovc13oBsWmJ7d3pK6g@mail.gmail.com> (message from Simon Glass on Tue, 1 Feb 2022 08:42:35 -0700)
> From: Simon Glass <sjg@chromium.org>
> Date: Tue, 1 Feb 2022 08:42:35 -0700
>
> It seems that rk3399 uses bl31.elf and splits out the sections into
> pieces. What a mess! I wonder if that is necessary for ATF to work? It
> seems to do the same for TEE.
That's because bl31.elf really consists of three binary blobs packed
together into a single ELF object. This is done such that specific
bits needed for suspend/resume land in the AP's SRAM and the PMU's
SRAM while the majority lands in DRAM. The splitting happens to make
U-Boot's ITS stuff happy.
I suppose this could be done in a different way by packing the ELF
binary itself into the FIT image, but then SPL has to parse the ELF
headers and copy things in place which may be challenging.
(I'm not familliar with the TEE stuff)
next prev parent reply other threads:[~2022-02-01 16:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 15:52 [PATCH v2 1/2] Makefile: Create a file to indicate the config Simon Glass
2022-01-30 15:52 ` [PATCH v2 2/2] Makefile: Don't allow new boards with SPL_FIT_GENERATOR Simon Glass
2022-01-30 19:40 ` Michal Simek
2022-01-30 23:14 ` Simon Glass
2022-01-31 14:24 ` Tom Rini
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:15 ` Tom Rini
2022-01-31 17:27 ` Simon Glass
2022-01-31 18:00 ` Tom Rini
2022-01-31 19:57 ` Simon Glass
2022-01-31 20:40 ` Tom Rini
2022-01-31 21:22 ` Simon Glass
2022-01-31 22:05 ` Tom Rini
2022-01-31 22:59 ` Simon Glass
2022-01-31 23:25 ` Tom Rini
2022-01-31 23:32 ` Tom Rini
2022-02-01 14:05 ` Simon Glass
2022-02-01 15:42 ` Simon Glass
2022-02-01 16:08 ` Mark Kettenis [this message]
2022-02-01 16:24 ` Simon Glass
2022-01-31 22:02 ` Mark Kettenis
2022-01-31 14:24 ` [PATCH v2 1/2] Makefile: Create a file to indicate the config Tom Rini
2022-01-31 16:13 ` Simon Glass
2022-01-31 16:21 ` Tom Rini
2022-01-31 17:27 ` Simon Glass
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=d3cbf782e80b057d@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=marek.behun@nic.cz \
--cc=monstr@monstr.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox