All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb.
Date: Fri, 14 Apr 2017 13:49:45 -0700	[thread overview]
Message-ID: <87wpamlno6.fsf@aikidev.net> (raw)
In-Reply-To: <20170412213510.GP19897@bill-the-cat>

On 2017-04-12, Tom Rini wrote:
> We also need to start setting bootm_size.  Quoting myself from
> include/configs/ti_armv7_common.h:
> /*
>  * We setup defaults based on constraints from the Linux kernel, which should
>  * also be safe elsewhere.  We have the default load at 32MB into DDR (for
>  * the kernel), FDT above 128MB (the maximum location for the end of the
>  * kernel), and the ramdisk 512KB above that (allowing for hopefully never
>  * seen large trees).  We say all of this must be within the first 256MB
>  * as that will normally be within the kernel lowmem and thus visible via
>  * bootm_size and we only run on platforms with 256MB or more of memory.
>  */
> ...
>         "bootm_size=0x10000000\0" \

I mostly add the variables defined in doc/README.distro for boards I'm
adding distro_bootcmd support to, and there's no mention of bootm_size
there.

Are there other places that it would make more sense to document or add
documentation for this variable setting?

Does bootm_size impact bootz/booti as well, or is it just used with
bootm?


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170414/b8412291/attachment.sig>

  reply	other threads:[~2017-04-14 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:28 [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb Vagrant Cascadian
2017-04-12 21:35 ` Tom Rini
2017-04-14 20:49   ` Vagrant Cascadian [this message]
2017-04-12 21:35 ` Andreas Färber
2017-04-12 23:59   ` Vagrant Cascadian
2017-04-16 21:27     ` Vagrant Cascadian

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=87wpamlno6.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --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.