On Fri, Mar 28, 2014 at 10:11:20AM -0600, Stephen Warren wrote: > 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?
No, because it's a per-arch thing on if you can have a ramdisk in high memory or not (and then the kernel deals with it), iirc. I _think_ this is one of those cases where ARM is much more strict about things than other architectures, but I lack the easy access to other platforms that I used to have. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
