From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/3] k3: am62x: image size fixes
Date: Mon, 18 May 2026 15:33:14 +0200 [thread overview]
Message-ID: <177911119402.41401.13308795856639038148.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260518-k3-am62x-image-size-fixes-v1-0-ab723d79922d@pengutronix.de>
On Mon, 18 May 2026 11:26:37 +0200, Sascha Hauer wrote:
> With the current configuration the initial barebox image for the AM62x
> is limited to 0x3a800 bytes. the current image fits well into it, but
> Let's make a bit more space available by moving DMDATA up to offset
> 0x3d000 giving us another 10KiB for the initial barebox image. Also set
> CONFIG_BAREBOX_MAX_IMAGE_SIZE in the k3-r5_defconfig to 0x3d000 to not
> exceed this limit unnoticed.
>
> [...]
Applied, thanks!
[1/3] ARM: k3: am62x: move stack to end of SRAM
https://git.pengutronix.de/cgit/barebox/commit/?id=a117841b9b9a (link may not be stable)
[2/3] ARM: k3: am62x: make more space for r5 barebox binary
https://git.pengutronix.de/cgit/barebox/commit/?id=14a7948a067e (link may not be stable)
[3/3] ARM: k3: k3-r5_defconfig: limit image size to maximum available space
https://git.pengutronix.de/cgit/barebox/commit/?id=6446c59dbc5d (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-05-18 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 9:26 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 ` [PATCH 3/3] ARM: k3: k3-r5_defconfig: limit image size to maximum available space Sascha Hauer
2026-05-18 9:37 ` Ahmad Fatoum
2026-05-18 10:38 ` Sascha Hauer
2026-05-18 13:33 ` 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=177911119402.41401.13308795856639038148.b4-ty@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