From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Stephen Warren <swarren@nvidia.com>,
Matthias Brugger <mbrugger@suse.com>,
Simon Glass <sjg@chromium.org>,
Peter Robinson <pbrobinson@gmail.com>
Subject: [PATCH v3 2/5] rpi: Set bootm_size to 512MB
Date: Mon, 9 Dec 2024 12:55:24 -0700 [thread overview]
Message-ID: <20241209195528.730260-3-sjg@chromium.org> (raw)
In-Reply-To: <20241209195528.730260-1-sjg@chromium.org>
Set this option so that all boot images stay within the bottom 512MB of
memory. This should allow us to drop the fdt_high and initrd_high
options.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
Suggested-by: Tom Rini <trini@konsulko.com>
---
Changes in v3:
- Add to the existing comment block
Changes in v2:
- Add new patch to set bootm_size
board/raspberrypi/rpi/rpi.env | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/board/raspberrypi/rpi/rpi.env b/board/raspberrypi/rpi/rpi.env
index 30228285edd..a327fccc77f 100644
--- a/board/raspberrypi/rpi/rpi.env
+++ b/board/raspberrypi/rpi/rpi.env
@@ -60,7 +60,12 @@ dfu_alt_info+=zImage fat 0 1
* Even with the smallest possible CPU-GPU memory split of the CPU getting
* only 64M, the remaining 25M starting at 0x02700000 should allow quite
* large initrds before they start colliding with U-Boot.
+ *
+ * Limit bootm_size to 512MB so that all boot images stay within the bottom
+ * 512MB of memory
*/
+bootm_size=0x20000000
+
#ifdef CONFIG_ARM64
fdt_high=ffffffffffffffff
initrd_high=ffffffffffffffff
--
2.34.1
next prev parent reply other threads:[~2024-12-09 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 19:55 [PATCH v3 0/5] rpi: Tidy up booting Simon Glass
2024-12-09 19:55 ` [PATCH v3 1/5] rpi: Add myself to the list of maintainers Simon Glass
2024-12-09 23:02 ` Peter Robinson
2024-12-09 19:55 ` Simon Glass [this message]
2024-12-10 11:16 ` [PATCH v3 2/5] rpi: Set bootm_size to 512MB Jaehoon Chung
2024-12-11 16:27 ` Peter Robinson
2024-12-11 16:57 ` Tom Rini
2024-12-11 17:26 ` Simon Glass
2024-12-16 15:16 ` Simon Glass
2024-12-09 19:55 ` [PATCH v3 3/5] rpi: Drop fdt_high and initrd_high Simon Glass
2024-12-10 11:16 ` Jaehoon Chung
2024-12-09 19:55 ` [PATCH v3 4/5] rpi: Update environment to support booti and large initrd Simon Glass
2024-12-10 11:17 ` Jaehoon Chung
2024-12-09 19:55 ` [PATCH v3 5/5] rpi: Use the U-Boot control FDT for fdt_addr Simon Glass
2024-12-10 11:17 ` Jaehoon Chung
2024-12-11 16:36 ` Peter Robinson
2024-12-16 0:27 ` Simon Glass
2024-12-18 16:26 ` Peter Robinson
2025-01-09 15:07 ` Simon Glass
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=20241209195528.730260-3-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=mbrugger@suse.com \
--cc=pbrobinson@gmail.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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