From: Christopher Obbard <christopher.obbard@linaro.org>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Stephen Warren <swarren@nvidia.com>,
Matthias Brugger <mbrugger@suse.com>,
Tom Rini <trini@konsulko.com>,
Peter Robinson <pbrobinson@gmail.com>
Subject: Re: [PATCH v4 3/5] rpi: Drop fdt_high and initrd_high
Date: Sun, 30 Mar 2025 15:07:30 +0100 [thread overview]
Message-ID: <4e3963dacbbe38af1bba9bc3faedc69c3cf2c9c8.camel@linaro.org> (raw)
In-Reply-To: <20241220003447.2913443-4-sjg@chromium.org>
Hi Simon,
[resending as I used the wrong e-mail address which isn't on the list,
oops]
On Thu, 2024-12-19 at 17:34 -0700, Simon Glass wrote:
> These are not needed now since there is a bootm_size setting to keep
> things within the lower part of memory.
>
> Drop them.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Tom Rini <trini@konsulko.com>
> Suggested-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Christopher Obbard <christopher.obbard@linaro.org>
Tested-by: Christopher Obbard <christopher.obbard@linaro.org> # CM4 1G
> ---
>
> (no changes since v2)
>
> Changes in v2:
> - Add new patch to drop fdt_high and initrd_high
>
> board/raspberrypi/rpi/rpi.env | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/board/raspberrypi/rpi/rpi.env
> b/board/raspberrypi/rpi/rpi.env
> index a327fccc77f..9b9fad82828 100644
> --- a/board/raspberrypi/rpi/rpi.env
> +++ b/board/raspberrypi/rpi/rpi.env
> @@ -66,13 +66,6 @@ dfu_alt_info+=zImage fat 0 1
> */
> bootm_size=0x20000000
>
> -#ifdef CONFIG_ARM64
> -fdt_high=ffffffffffffffff
> -initrd_high=ffffffffffffffff
> -#else
> -fdt_high=ffffffff
> -initrd_high=ffffffff
> -#endif
> kernel_addr_r=0x00080000
> scriptaddr=0x02400000
> pxefile_addr_r=0x02500000
next prev parent reply other threads:[~2025-03-30 14:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 0:34 [PATCH v4 0/5] rpi: Tidy up booting Simon Glass
2024-12-20 0:34 ` [PATCH v4 1/5] rpi: Add myself to the list of maintainers Simon Glass
2025-03-30 13:37 ` Christopher Obbard
2025-04-21 10:09 ` Peter Robinson
2025-05-23 20:20 ` Simon Glass
2024-12-20 0:34 ` [PATCH v4 2/5] rpi: Set bootm_size to 512MB Simon Glass
2025-03-30 13:35 ` Christopher Obbard
2025-04-21 10:09 ` Peter Robinson
2024-12-20 0:34 ` [PATCH v4 3/5] rpi: Drop fdt_high and initrd_high Simon Glass
2025-03-30 13:35 ` Christopher Obbard
2025-03-30 14:07 ` Christopher Obbard [this message]
2025-04-21 10:10 ` Peter Robinson
2024-12-20 0:34 ` [PATCH v4 4/5] rpi: Update environment to support booti and large initrd Simon Glass
2025-03-30 13:35 ` Christopher Obbard
2025-03-30 14:07 ` Christopher Obbard
2025-04-21 10:09 ` Peter Robinson
2024-12-20 0:34 ` [PATCH v4 5/5] rpi: Use the U-Boot control FDT for fdt_addr Simon Glass
2025-03-30 13:36 ` Christopher Obbard
2025-03-30 14:07 ` Christopher Obbard
2025-04-21 10:34 ` Peter Robinson
2025-05-23 20:20 ` Simon Glass
2025-01-15 14:09 ` [PATCH v4 0/5] rpi: Tidy up booting Simon Glass
2025-01-30 19:54 ` Simon Glass
2025-02-03 3:41 ` Peter Robinson
2025-03-30 13:29 ` Christopher Obbard
2025-03-30 15:03 ` Christopher Obbard
2025-04-01 15:51 ` 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=4e3963dacbbe38af1bba9bc3faedc69c3cf2c9c8.camel@linaro.org \
--to=christopher.obbard@linaro.org \
--cc=mbrugger@suse.com \
--cc=pbrobinson@gmail.com \
--cc=sjg@chromium.org \
--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