From: Tom Rini <trini@konsulko.com>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: ggiordano@phytec.com, w.egorov@phytec.de, u-boot@lists.denx.de,
joe.hershberger@ni.com, bb@ti.com, nmorrisson@phytec.com,
upstream@lists.phytec.de
Subject: Re: [PATCH 3/3] board: phytec: phycore_am62ax: Update Environment
Date: Mon, 28 Apr 2025 10:10:51 -0600 [thread overview]
Message-ID: <20250428161051.GC5495@bill-the-cat> (raw)
In-Reply-To: <20250428144904.1058574-3-d.schultz@phytec.de>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On Mon, Apr 28, 2025 at 07:49:04AM -0700, Daniel Schultz wrote:
> Add fit_addr_r to the environment to allow us to boot from a FIT image.
>
> 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_am62ax/phycore_am62ax.env | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
What is the minimum memory configuration you have to work with here?
That's still a very small window unless you're shipping modules with
512MiB or so.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-04-28 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 14:49 [PATCH 1/3] include: env: phytec: k3_net: Remove net_apply_extensions Daniel Schultz
2025-04-28 14:49 ` [PATCH 2/3] include: env: phytec: k3_net: Use get_cmd Daniel Schultz
2025-04-28 14:49 ` [PATCH 3/3] board: phytec: phycore_am62ax: Update Environment Daniel Schultz
2025-04-28 16:10 ` Tom Rini [this message]
2025-04-29 12:14 ` Daniel Schultz
2025-04-29 14:17 ` Tom Rini
2025-05-07 15:24 ` [PATCH 1/3] include: env: phytec: k3_net: Remove net_apply_extensions 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=20250428161051.GC5495@bill-the-cat \
--to=trini@konsulko.com \
--cc=bb@ti.com \
--cc=d.schultz@phytec.de \
--cc=ggiordano@phytec.com \
--cc=joe.hershberger@ni.com \
--cc=nmorrisson@phytec.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