From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] v7a: images: stm32mp: double STM32MP15 fip partition size to 2M
Date: Wed, 4 Jun 2025 11:44:36 +0200 [thread overview]
Message-ID: <be6278f6-f806-4ef1-9f8e-44b187d5e64f@pengutronix.de> (raw)
In-Reply-To: <1749029124-18d5039ed4d170c7ec330ccc@pty>
Hello Roland,
On 6/4/25 11:28, Roland Hieber wrote:
> On Mon, Jun 02, 2025 at 10:12:32AM +0200, Ahmad Fatoum wrote:
>> Our FIP image contains barebox as non-trusted firmware, a hardware
>> device tree and a very small firmware config as well as the secure
>> monitor, either from TF-A or OP-TEE.
>>
>> This clocks in at 617K for STM32MP15, where we don't use OP-TEE and 986K
>> on STM32MP13, where we do use it.
>>
>> The STM32MP13 has a separate genimage config, which has a 2M FIP
>> partition already. Let's follow suit for STM32MP15 to allow for more
>> convenient experimentation and debugging, e.g. enabling Kernel
>> AddressSanitizer in barebox already makes it to big to fit inside a 1M
>> fip partition.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>
> Note: this is already effectively included in my barebox unification series:
> <20250526101147.1953428-5-rhi@pengutronix.de> (2025-05-26, Roland Hieber:
> "[DistroKit] [PATCH 05/11] v7a: stm32mp: switch to upstream barebox recipe")
> (where the size of the partition is removed in favour of specifying it in the
> fit image config).
Nice, this patch can be disregarded then.
Thanks,
Ahmad
>
> - Roland
>
>> ---
>> configs/platform-v7a/config/images/stm32mp.config | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/configs/platform-v7a/config/images/stm32mp.config b/configs/platform-v7a/config/images/stm32mp.config
>> index 888f83b360b1..8f784ad8b9fc 100644
>> --- a/configs/platform-v7a/config/images/stm32mp.config
>> +++ b/configs/platform-v7a/config/images/stm32mp.config
>> @@ -16,7 +16,7 @@ image @IMAGE@ {
>> }
>> partition fip {
>> image = "@STM32MP_BOARD@@SCMI@.fip"
>> - size = 1M
>> + size = 2M
>> }
>>
>> partition barebox-environment {
>> --
>> 2.39.5
>
--
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 |
prev parent reply other threads:[~2025-06-04 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 8:12 Ahmad Fatoum
2025-06-04 9:28 ` Roland Hieber
2025-06-04 9:44 ` Ahmad Fatoum [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=be6278f6-f806-4ef1-9f8e-44b187d5e64f@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=rhi@pengutronix.de \
/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