From: Daniel Schultz <d.schultz@phytec.de>
To: <w.egorov@phytec.de>, <trini@konsulko.com>, <u-boot@lists.denx.de>
Cc: <upstream@lists.phytec.de>, Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 4/4] board: Phytec: phycore_am62x: Increase size for Image in SPI
Date: Mon, 10 Feb 2025 07:25:48 -0800 [thread overview]
Message-ID: <20250210152548.1263498-4-d.schultz@phytec.de> (raw)
In-Reply-To: <20250210152548.1263498-1-d.schultz@phytec.de>
Increase the maximum Image size from 23 MB to 26 MB by moving the
initramfs start address up. This gives us a bigger ranger to
provide kernel images which are not stripped down too much.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
board/phytec/phycore_am62x/phycore_am62x.env | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/phytec/phycore_am62x/phycore_am62x.env b/board/phytec/phycore_am62x/phycore_am62x.env
index 711ca3040c4..024f38ebba3 100644
--- a/board/phytec/phycore_am62x/phycore_am62x.env
+++ b/board/phytec/phycore_am62x/phycore_am62x.env
@@ -22,4 +22,4 @@ get_cmd=tftp
spi_fdt_addr=0x700000
spi_image_addr=0x800000
-spi_ramdisk_addr=0x1e00000
+spi_ramdisk_addr=0x2200000
--
2.25.1
next prev parent reply other threads:[~2025-02-10 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:25 [PATCH 1/4] configs: phycore_am64x_a53_defconfig: Enable ENV_IS_IN_SPI_FLASH Daniel Schultz
2025-02-10 15:25 ` [PATCH 2/4] configs: phycore_am62x_a53_defconfig: " Daniel Schultz
2025-02-11 3:47 ` Wadim Egorov
2025-02-10 15:25 ` [PATCH 3/4] board: Phytec: phycore_am64x: Increase size for Image in SPI Daniel Schultz
2025-02-11 3:47 ` Wadim Egorov
2025-02-10 15:25 ` Daniel Schultz [this message]
2025-02-11 3:47 ` [PATCH 4/4] board: Phytec: phycore_am62x: " Wadim Egorov
2025-02-11 3:46 ` [PATCH 1/4] configs: phycore_am64x_a53_defconfig: Enable ENV_IS_IN_SPI_FLASH Wadim Egorov
2025-02-21 3:28 ` Tom Rini
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=20250210152548.1263498-4-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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