Kim Phillips wrote:
On Tue, 15 Apr 2008 13:10:29 +0800 Dave Liu r63238@freescale.com wrote:
Update the default load address. if not, the kernel image will be overwritten when u-boot boot the latest linux kernel.
Signed-off-by: Dave Liu daveliu@freescale.com
include/configs/MPC837XEMDS.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/configs/MPC837XEMDS.h b/include/configs/MPC837XEMDS.h index 7fc0f7e..b2b4aa1 100644 --- a/include/configs/MPC837XEMDS.h +++ b/include/configs/MPC837XEMDS.h @@ -595,7 +595,7 @@
#define CONFIG_BAUDRATE 115200
-#define CONFIG_LOADADDR 200000 /* default location for tftp and bootm */ +#define CONFIG_LOADADDR 2000000 /* default location for tftp and bootm */
#define CONFIG_BOOTDELAY 6 /* -1 disables auto-boot */ #undef CONFIG_BOOTARGS /* the boot command will set bootargs */ @@ -605,7 +605,7 @@ "consoledev=ttyS0\0" \ "ramdiskaddr=1000000\0" \ "ramdiskfile=ramfs.83xx\0" \
- "fdtaddr=400000\0" \
- "fdtaddr=3000000\0" \
is such a drastic difference really necessary? how about we double them instead?
Kim
Hi Kim, Dave,
The current recommended practice on the denx.de wiki is to have a 12K FDT blob (0x3000). My latest personal convention for memory locations is to put the FDT blob at a semi-arbitrary base address and set the loadaddr 32K higher (could use 64K if we want to be paranoid about blob growth). The advantage is that the kernel can grow or shrink (ha!) fairly often, but the blob should remain fairly small and fairly constant.
This is better than dropping pieces all over memory.
This is what I've been running lately: setenv fdtaddr 400000 setenv loadaddr 408000 setenv ramdiskaddr 1000000
Best regards, gvb