From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Fri, 28 Mar 2014 10:11:20 -0600 Subject: [U-Boot] [PATCH 1/6] add README.distro file In-Reply-To: <20140328154222.GN16360@bill-the-cat> References: <1392659798-1665-1-git-send-email-dennis@ausil.us> <1395353581-5839-1-git-send-email-dennis@ausil.us> <1395353581-5839-2-git-send-email-dennis@ausil.us> <5331E5EE.1040906@wwwdotorg.org> <20140328154222.GN16360@bill-the-cat> Message-ID: <53359F28.5000400@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 03/28/2014 09:42 AM, Tom Rini wrote: > On Tue, Mar 25, 2014 at 02:24:14PM -0600, Stephen Warren wrote: >> On 03/20/2014 04:12 PM, Dennis Gilmore wrote: > [snip] >>> +You should not set initrd_high and fdt_high to 0xffffffff as the user should >>> +not need to edit the memory locations having the initramfs and dtb being >>> +relocatable is best to ensure the system will boot in all situations. >> >> Perhaps CONFIG_SYS_BOOTMAPSZ is worth a mention too. The commit >> description for 7f1b767aea94 "ARM: tegra: define CONFIG_SYS_BOOTMAPSZ" >> might be useful when writing this part of the document. > > I would swear (and I just dug up the notes from the last time I was > looking at this) that no, CONFIG_SYS_BOOTMAPSZ is not sufficient because > it doesn't cover the ramdisk case, which is important for generic > distro, unless you also add in initrd_high=top-of-lowmem-value or know > it'll be in an always-good spot and set it to 0xffffffff. Isn't that a bug? In other words, shouldn't CONFIG_SYS_BOOTMAPSZ affect a ramdisk too?