From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/7] ARM: stm32mp: bbu: add FIP update handler
Date: Fri, 3 Jun 2022 09:17:42 +0200 [thread overview]
Message-ID: <20220603071742.GH1615@pengutronix.de> (raw)
In-Reply-To: <20220602090133.3190450-1-a.fatoum@pengutronix.de>
On Thu, Jun 02, 2022 at 11:01:26AM +0200, Ahmad Fatoum wrote:
> STM32MP1 BootROM boots from GPT partition fsbl1 or fsbl2 on SD-Card and
> from boot partition on eMMC. Recent TF-A without legacy image support will
> then look in a GPT partition named fip in the user area.
>
> With recent patches[1], TF-A will also check offset SZ_256K in the boot
> partition to see if the FIP is there.
>
> Add a barebox_update handler that covers these scenarios.
>
> The TF-A patches are not yet upstream, but have all maintainer ACKs and
> will likely be part of TF-A v2.8.
>
> [1]: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/15332
>
> Ahmad Fatoum (7):
> bbu: move barebox_update eMMC boot handling into common code
> bbu: use free(NULL) to simplify function cleanup
> bbu: add flag for enabling eMMC boot ack
> bbu: export bbu_std_file_handler for use in custom handlers
> filetype: differentiate between STM32MP FSBL and SSBL images
> ARM: stm32mp: bbu: add FIP update handler
> fastboot: support TF-A FSBL and FIP images for barebox update
Applied, thanks
Sascha
>
> arch/arm/mach-imx/imx-bbu-internal.c | 48 +-----
> arch/arm/mach-stm32mp/Makefile | 1 +
> arch/arm/mach-stm32mp/bbu.c | 197 +++++++++++++++++++++++
> arch/arm/mach-stm32mp/include/mach/bbu.h | 18 ++-
> arch/arm/mach-stm32mp/stm32image.c | 2 +-
> common/bbu.c | 100 ++++++++++--
> common/filetype.c | 15 +-
> include/bbu.h | 7 +
> include/filetype.h | 3 +-
> 9 files changed, 327 insertions(+), 64 deletions(-)
> create mode 100644 arch/arm/mach-stm32mp/bbu.c
>
> --
> 2.30.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-06-03 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:01 Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 1/7] bbu: move barebox_update eMMC boot handling into common code Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 2/7] bbu: use free(NULL) to simplify function cleanup Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 3/7] bbu: add flag for enabling eMMC boot ack Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 4/7] bbu: export bbu_std_file_handler for use in custom handlers Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 5/7] filetype: differentiate between STM32MP FSBL and SSBL images Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 6/7] ARM: stm32mp: bbu: add FIP update handler Ahmad Fatoum
2022-06-02 9:01 ` [PATCH 7/7] fastboot: support TF-A FSBL and FIP images for barebox update Ahmad Fatoum
2022-06-03 7:17 ` 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=20220603071742.GH1615@pengutronix.de \
--to=sha@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