@Eric: also, we currently use different load addresses in the live images: uboot_kernel_addr="0x00200000" uboot_ramdisk_addr="0x01100000" uboot_script_addr="0x1000"
the boot script being:
if test -n \${fs} && test -n \${interface} && test -n \${device}; then
\${fs}load \${interface} \${device} $uboot_kernel_addr $uboot_kernel
\${fs}load \${interface} \${device} $uboot_ramdisk_addr $uboot_initrd
setenv bootargs quiet splash $DEFAULT_PRESEED $uboot_extra_cmdline
bootm $uboot_kernel_addr $uboot_ramdisk_addr
fi
@Eric: also, we currently use different load addresses in the live images:
uboot_ kernel_ addr="0x0020000 0"
uboot_ ramdisk_ addr="0x0110000 0"
uboot_ script_ addr="0x1000"
the boot script being: extra_cmdline
if test -n \${fs} && test -n \${interface} && test -n \${device}; then
\${fs}load \${interface} \${device} $uboot_kernel_addr $uboot_kernel
\${fs}load \${interface} \${device} $uboot_ramdisk_addr $uboot_initrd
setenv bootargs quiet splash $DEFAULT_PRESEED $uboot_
bootm $uboot_kernel_addr $uboot_ramdisk_addr
fi
Do these need to be fixed as well?