From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/7] ARM: add support for chainloading barebox inside FIP images
Date: Tue, 22 Apr 2025 17:04:17 +0200 [thread overview]
Message-ID: <174533425720.2394443.15655403946614262641.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250409140134.2079552-1-a.fatoum@pengutronix.de>
On Wed, 09 Apr 2025 16:01:28 +0200, Ahmad Fatoum wrote:
> For use on the STM32MP1, add a bootm handler for chainloading FIP
> images. This removes the last remaining use case for SSBL .stm32 images,
> after TF-A had dropped support late 2022.
>
> Ahmad Fatoum (7):
> fip: add struct fip_image_desc::private_data
> fip: mark predefined toc_entries array const
> bootm: implement UIMAGE_IS_ADDRESS_VALID helper
> ARM: legacy: make architecture number unsigned
> ARM: introduce jump_to_linux helper
> ARM: add support for chainloading barebox inside FIP images
> ARM: stm32mp: retire non-FIP stm32mp_bbu_mmc_register_handler
>
> [...]
Applied, thanks!
[1/7] fip: add struct fip_image_desc::private_data
https://git.pengutronix.de/cgit/barebox/commit/?id=5c3a7fe64fed (link may not be stable)
[2/7] fip: mark predefined toc_entries array const
https://git.pengutronix.de/cgit/barebox/commit/?id=93c14dd7b326 (link may not be stable)
[3/7] bootm: implement UIMAGE_IS_ADDRESS_VALID helper
https://git.pengutronix.de/cgit/barebox/commit/?id=879208beff0b (link may not be stable)
[4/7] ARM: legacy: make architecture number unsigned
https://git.pengutronix.de/cgit/barebox/commit/?id=bd4a7b8edd41 (link may not be stable)
[5/7] ARM: introduce jump_to_linux helper
https://git.pengutronix.de/cgit/barebox/commit/?id=26ddae22a001 (link may not be stable)
[6/7] ARM: add support for chainloading barebox inside FIP images
https://git.pengutronix.de/cgit/barebox/commit/?id=c33636a0f165 (link may not be stable)
[7/7] ARM: stm32mp: retire non-FIP stm32mp_bbu_mmc_register_handler
https://git.pengutronix.de/cgit/barebox/commit/?id=df119b0af6bd (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-04-22 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:01 Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 1/7] fip: add struct fip_image_desc::private_data Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 2/7] fip: mark predefined toc_entries array const Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 3/7] bootm: implement UIMAGE_IS_ADDRESS_VALID helper Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 4/7] ARM: legacy: make architecture number unsigned Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 5/7] ARM: introduce jump_to_linux helper Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 6/7] ARM: add support for chainloading barebox inside FIP images Ahmad Fatoum
2025-04-09 14:01 ` [PATCH 7/7] ARM: stm32mp: retire non-FIP stm32mp_bbu_mmc_register_handler Ahmad Fatoum
2025-04-22 15:04 ` Sascha Hauer [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=174533425720.2394443.15655403946614262641.b4-ty@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