From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 3/3] ARM: k3: k3-r5_defconfig: limit image size to maximum available space
Date: Mon, 18 May 2026 11:26:40 +0200 [thread overview]
Message-ID: <20260518-k3-am62x-image-size-fixes-v1-3-ab723d79922d@pengutronix.de> (raw)
In-Reply-To: <20260518-k3-am62x-image-size-fixes-v1-0-ab723d79922d@pengutronix.de>
On the AM62x we have 0x3e000 bytes available for SBL usage. The upper
0x1000 bytes are used by the DMDATA, so set maximum image size to
0x3d000.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/configs/k3-r5_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/configs/k3-r5_defconfig b/arch/arm/configs/k3-r5_defconfig
index ece3d00947..6d8391c55e 100644
--- a/arch/arm/configs/k3-r5_defconfig
+++ b/arch/arm/configs/k3-r5_defconfig
@@ -8,7 +8,7 @@ CONFIG_ARM_OPTIMZED_STRING_FUNCTIONS=y
CONFIG_NAME="k3-r5_defconfig"
CONFIG_ENVIRONMENT_VARIABLES=y
CONFIG_IMAGE_COMPRESSION_XZKERN=y
-CONFIG_BAREBOX_MAX_IMAGE_SIZE=0x10000000
+CONFIG_BAREBOX_MAX_IMAGE_SIZE=0x3d000
CONFIG_MALLOC_SIZE=0x0
CONFIG_MALLOC_TLSF=y
CONFIG_KALLSYMS=y
--
2.47.3
next prev parent reply other threads:[~2026-05-18 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 9:26 [PATCH 0/3] k3: am62x: image size fixes Sascha Hauer
2026-05-18 9:26 ` [PATCH 1/3] ARM: k3: am62x: move stack to end of SRAM Sascha Hauer
2026-05-18 9:26 ` [PATCH 2/3] ARM: k3: am62x: make more space for r5 barebox binary Sascha Hauer
2026-05-18 9:41 ` Ahmad Fatoum
2026-05-18 9:26 ` Sascha Hauer [this message]
2026-05-18 9:37 ` [PATCH 3/3] ARM: k3: k3-r5_defconfig: limit image size to maximum available space Ahmad Fatoum
2026-05-18 10:38 ` Sascha Hauer
2026-05-18 13:33 ` [PATCH 0/3] k3: am62x: image size fixes 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=20260518-k3-am62x-image-size-fixes-v1-3-ab723d79922d@pengutronix.de \
--to=s.hauer@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