All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: u-boot <u-boot@lists.denx.de>
Cc: Adam Ford <aford173@gmail.com>,
	"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
	Peng Fan <peng.fan@nxp.com>,
	 Jagan Teki <jagan@amarulasolutions.com>,
	Matteo Lisi <matteo.lisi@engicam.com>,
	Fabio Estevam <festevam@gmail.com>,
	Stefano Babic <sbabic@denx.de>,
	Teresa Remmet <t.remmet@phytec.de>,
	 Oleksandr Suvorov <oleksandr.suvorov@toradex.com>,
	 Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Igor Opaniuk <igor.opaniuk@toradex.com>
Subject: imx8mm memory env in U-Boot
Date: Thu, 26 Aug 2021 09:39:20 -0700	[thread overview]
Message-ID: <CAJ+vNU13tm+rR=cyc4gULM=F=7zZf1Bt7o2YnVho-neRiRbMzQ@mail.gmail.com> (raw)

Greetings,

I'm trying to understand what the best memory usage is in U-Boot for
IMX8M boards for generic distro configs such as: loadaddr,
kernel_addr_r, fdt_addr_r, ramdisk_addr, scriptaddr.

My understanding is that the following is a good rule of thumb:
loadaddr = DDR start + 32MB (as FIT images may load kernel at DDR
start; but this only allows for a 32MB kernel)
kernel_addr_r = $loadaddr
fdt_addr_r = $kernel_addr_r + 128MB (allows you up to 128MB for your
kernel; handy if you want a kernel with internal ramdisk)
ramdisk_addr = fdt_addr_r + 512KB (512KB should be plenty for a dt)
scriptaddr = $loadaddr

Looking at the various imx8mm boards upstream they are kind of all
over the place but do follow some patterns likely due to some of us
just going with what prior boards used.

While I'm at it I've encountered a couple other questions:
- why on IMX8MM is CONFIG_LOADADDR is 0x40480000 when DDR starts at
0x40000000. Why the 4608KB offset?
- what is CONFIG_SYS_INIT_RAM_SIZE? Most boards are setting this to
2MB but a couple (cl-iot-gate/phycore) set it to 512KB
- what are people using for the load address for the kernel within FIT
images? I expect start of DDR is appropriate (0x40000000) however for
whatever reason I've been using 0x40200000. This plays into the env as
you can't overlap where you loaded the FIT image with where you told
the FIT image to relocate the kernel to.

Best regards,

Tim

             reply	other threads:[~2021-08-26 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 16:39 Tim Harvey [this message]
2021-08-26 19:41 ` imx8mm memory env in U-Boot Tom Rini
2021-08-27 21:32   ` Tim Harvey
2021-08-28 19:24     ` 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='CAJ+vNU13tm+rR=cyc4gULM=F=7zZf1Bt7o2YnVho-neRiRbMzQ@mail.gmail.com' \
    --to=tharvey@gateworks.com \
    --cc=aford173@gmail.com \
    --cc=festevam@gmail.com \
    --cc=igor.opaniuk@toradex.com \
    --cc=jagan@amarulasolutions.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=matteo.lisi@engicam.com \
    --cc=oleksandr.suvorov@toradex.com \
    --cc=paul.liu@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=t.remmet@phytec.de \
    --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.