From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/3] ARM: rockchip: boards: leave moving to the load address to atf.c
Date: Thu, 01 Oct 2026 10:19:36 +0000 [thread overview]
Message-ID: <6df2d906-147d-4e57-8fbd-b4951e02af90@pengutronix.de> (raw)
In-Reply-To: <5e5c848a-207c-45db-ad29-bf0b326badff@pengutronix.de>
On 2026-10-01 10:30, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 10/1/26 9:42 AM, Sascha Hauer wrote:
> > The SoC entry functions now move barebox to the load address themselves,
> > with the MMU enabled. Stop doing it upfront with relocate_to_adr_full(),
> > which copies the image with the MMU off, and just relocate in place.
> >
> > Assisted-by: Claude:claude-opus-5-5
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> Will an out-of-tree board that still has the same old pattern continue
> to work normally?
Yes. That board would relocate the binary in the board code and
rockchip_move_to_load_address() would bail out early due to
__image_start == load_address. The MMU would then be enabled in
rockchip_atf_load_bl31() as before.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-10-01 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 7:42 [PATCH 0/3] Rockchip: early boot time optimization Sascha Hauer
2026-10-01 7:42 ` [PATCH 1/3] ARM: rockchip: move to the load address with the MMU enabled Sascha Hauer
2026-10-01 7:42 ` [PATCH 2/3] ARM: rockchip: boards: leave moving to the load address to atf.c Sascha Hauer
2026-10-01 8:30 ` Ahmad Fatoum
2026-10-01 10:19 ` Sascha Hauer [this message]
2026-10-01 7:42 ` [PATCH 3/3] ARM: rockchip: pack the device tree passed to TF-A and OP-TEE Sascha Hauer
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=6df2d906-147d-4e57-8fbd-b4951e02af90@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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