From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vagrant Cascadian Date: Fri, 14 Apr 2017 13:49:45 -0700 Subject: [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb. In-Reply-To: <20170412213510.GP19897@bill-the-cat> References: <20170412212805.4626-1-vagrant@debian.org> <20170412213510.GP19897@bill-the-cat> Message-ID: <87wpamlno6.fsf@aikidev.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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: