All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1] imx: imx8qm: enable relocation of fdt and initrd
Date: Fri, 7 Feb 2020 11:46:11 +0100	[thread overview]
Message-ID: <20200207104611.GC9493@optiplex> (raw)
In-Reply-To: <20200205160506.GQ13379@bill-the-cat>

On 05/02/20, Tom Rini wrote:
> On Wed, Feb 05, 2020 at 03:51:42PM +0000, Oliver Graute wrote:
> 
> > Remove 'fdt_high' and 'initrd_high' environment variables (set to 0xFFFFFFFF)
> > from default environment which prevents relocation of FDT and initrd.
> > 
> > Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: Peng Fan <peng.fan@nxp.com>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: Ye Li <ye.li@nxp.com>
> > Cc: uboot-imx <uboot-imx@nxp.com>
> > ---
> >  include/configs/imx8qm_rom7720.h | 2 --
> >  1 file changed, 2 deletions(-)
> > 
> > diff --git a/include/configs/imx8qm_rom7720.h b/include/configs/imx8qm_rom7720.h
> > index 865863eb7c..8beb65e96b 100644
> > --- a/include/configs/imx8qm_rom7720.h
> > +++ b/include/configs/imx8qm_rom7720.h
> > @@ -63,11 +63,9 @@
> >  	"panel=NULL\0" \
> >  	"console=ttyLP0\0" \
> >  	"fdt_addr=0x83000000\0"			\
> > -	"fdt_high=0xffffffffffffffff\0"		\
> >  	"boot_fdt=try\0" \
> >  	"fdt_file=imx8qm-rom7720-a1.dtb\0" \
> >  	"initrd_addr=0x83800000\0"		\
> > -	"initrd_high=0xffffffffffffffff\0" \
> >  	"mmcdev="__stringify(CONFIG_SYS_MMC_ENV_DEV)"\0" \
> >  	"mmcpart=" __stringify(CONFIG_SYS_MMC_IMG_LOAD_PART) "\0" \
> >  	"mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \
> 
> Is bootm_size or CONFIG_SYS_BOOTMAPSZ already being set somewhere for
> these platforms?  In Linux, Documentation/arm64/booting.rst does
> describe limitations on where FDT/initrd can reside in memory so we need
> to make sure they're obeyed.  That's best done by using bootm_size in
> environment or CONFIG_SYS_BOOTMAPSZ at build time to ensure alignment
> and non-overlap within those limits and not "don't move anything ever"
> as fdt_high/initrd_high=0xff... does.  Thanks!

No currently not. Because I do not know the exact value I have to set
for CONFIG_SYS_BOOTMAPSZ here. How do I find that out for my board?

Best Regards,

Oliver

  reply	other threads:[~2020-02-07 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 15:51 [PATCH v1] imx: imx8qm: enable relocation of fdt and initrd Oliver Graute
2020-02-05 16:05 ` Tom Rini
2020-02-07 10:46   ` Oliver Graute [this message]
2020-02-07 14: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=20200207104611.GC9493@optiplex \
    --to=oliver.graute@gmail.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.