lsxl: use default load addresses for legacy boot

The load addresses for the bootcmd_legacy script were taken from the
original bootloader from Buffalo. But newer kernels are too big and the
uncompressing will overwrite parts of the initial ramdisk. Therefore,
we switch to the load addresses which are also used by the other boot
script.

Signed-off-by: Michael Walle <michael@walle.cc>
This commit is contained in:
Michael Walle 2015-02-08 20:06:05 +01:00 committed by Luka Perkov
parent bd2a4888b1
commit bc2ad9f04d

View file

@ -127,9 +127,9 @@
"ramdisk_addr=0x01000000\0" \ "ramdisk_addr=0x01000000\0" \
"fdt_addr=0x01ff0000\0" \ "fdt_addr=0x01ff0000\0" \
"bootcmd_legacy=ide reset " \ "bootcmd_legacy=ide reset " \
"&& load ide ${hdpart} 0x00100000 /uImage.buffalo " \ "&& load ide ${hdpart} ${kernel_addr} /uImage.buffalo " \
"&& load ide ${hdpart} 0x00800000 /initrd.buffalo " \ "&& load ide ${hdpart} ${ramdisk_addr} /initrd.buffalo "\
"&& bootm 0x00100000 0x00800000\0" \ "&& bootm ${kernel_addr} ${ramdisk_addr}\0" \
"bootcmd_net=bootp ${kernel_addr} uImage " \ "bootcmd_net=bootp ${kernel_addr} uImage " \
"&& tftpboot ${ramdisk_addr} uInitrd " \ "&& tftpboot ${ramdisk_addr} uInitrd " \
"&& tftpboot ${fdt_addr} " CONFIG_FDTFILE " " \ "&& tftpboot ${fdt_addr} " CONFIG_FDTFILE " " \