Please try setenv initrd_high 0
But this is only a workaround for the issue? The problem is not the initrd, but the OF tree, which is located just below the initrd in memory. If the initrd is now within the first CFG_BOOTMAPSZ limit, then the OF tree is as well and the issue disappears...all I want is that the OF tree is within the limit, I dont care where the initrd is. (BTW what happens if the initrd image is bigger then the CFG_BOOTMAPSZ limit?)
Regards, Torsten
Hi,
I want to use an initrd on a MPC85xx processor with 512MB
RAM. U-boot
uses CONFIG_OF_FLAT_TREE to provide the bootargs to the kernel. I found out, that the Linux kernel crashes at the first access to the OF tree in memory. It seems that it's because the OF tree is located just below the initrd in memory, but the Linux kernel maps only the first 16MByte at startup. (When no initrd is used the OF tree is located differently - the kernel starts without problems.) Is there a reason for this different mapping scheme? Did I missed something? Shall we patch u-boot or the kernel?
Thanks for your help.
Torsten
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge &CID=DEVDEV _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge
&CID=DEVDEV _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users