All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Majewski" <lukma@nabladev.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] mccmon6: Stop disabling device tree relocation
Date: Wed, 19 Nov 2025 10:41:49 +0100	[thread overview]
Message-ID: <20251119104149.64c1fb2e@wsk> (raw)
In-Reply-To: <20251118180404.591132-1-trini@konsulko.com>

On Tue, 18 Nov 2025 12:04:04 -0600
Tom Rini <trini@konsulko.com> wrote:

> Remove setting of fdt_high to ~0, which disables device tree
> relocation, from the default environment. Doing so prevents U-Boot
> from correcting problems such as having an unaligned device tree and
> leads to various failure modes in the OS.
> 
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> If there is some window of memory that must be used for where the
> device tree is relocated to, bootm_low + bootm_size (or often just
> bootm_size) or bootm_mapsize are the correct way do this. Please see
> doc/usage/environment.rst for more details.
> 
> Cc: Lukasz Majewski <lukma@nabladev.com>
> 
> ---
>  include/configs/mccmon6.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/include/configs/mccmon6.h b/include/configs/mccmon6.h
> index b64bf93bcb74..9f401718bfb4 100644
> --- a/include/configs/mccmon6.h
> +++ b/include/configs/mccmon6.h
> @@ -35,7 +35,6 @@
>  
>  #define CFG_EXTRA_ENV_SETTINGS \
>  	"console=ttymxc0,115200 quiet\0" \
> -	"fdt_high=0xffffffff\0" \
>  	"initrd_high=0xffffffff\0" \
>  	"boot_os=yes\0" \
>  	"kernelsize=0x300000\0" \

Reviewed-by: Łukasz Majewski <lukma@nabladev.com>

-- 
Best regards,

Lukasz Majewski

--
Nabla Software Engineering GmbH
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Managing Director : Stefano Babic

      reply	other threads:[~2025-11-19  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 18:04 [PATCH] mccmon6: Stop disabling device tree relocation Tom Rini
2025-11-19  9:41 ` Łukasz Majewski [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=20251119104149.64c1fb2e@wsk \
    --to=lukma@nabladev.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.