km/common: use u-boot.kwb for u-boot update function on arm
Now we use the standard u-boot make to build the Kirkwood binary. The output file is u-boot.kwb. So use this name for the tftp update function to avoid confusion, because this is the binary we need on Kirkwood. Signed-off-by: Holger Brunck <holger.brunck@keymile.com> cc: Valentin Longchamp <valentin.longchamp@keymile.com> cc: Heiko Schocher <hs@denx.de> cc: Wolfgang Denk <wd@denx.de>
This commit is contained in:
parent
9485e779a3
commit
8519d18035
3 changed files with 2 additions and 1 deletions
|
@ -248,7 +248,6 @@
|
||||||
"stderr=serial\0" \
|
"stderr=serial\0" \
|
||||||
"stdin=serial\0" \
|
"stdin=serial\0" \
|
||||||
"stdout=serial\0" \
|
"stdout=serial\0" \
|
||||||
"u-boot="xstr(CONFIG_HOSTNAME) "/u-boot.bin\0" \
|
|
||||||
""
|
""
|
||||||
#endif /* CONFIG_KM_DEF_ENV */
|
#endif /* CONFIG_KM_DEF_ENV */
|
||||||
|
|
||||||
|
|
|
@ -75,6 +75,7 @@
|
||||||
"cramfsload ${fdt_addr_r} " \
|
"cramfsload ${fdt_addr_r} " \
|
||||||
"fdt_0x${IVM_BoardId}_0x${IVM_HWKey}.dtb\0" \
|
"fdt_0x${IVM_BoardId}_0x${IVM_HWKey}.dtb\0" \
|
||||||
"fdt_addr_r=" xstr(CONFIG_KM_FDT_ADDR) "\0" \
|
"fdt_addr_r=" xstr(CONFIG_KM_FDT_ADDR) "\0" \
|
||||||
|
"u-boot="xstr(CONFIG_HOSTNAME) "/u-boot.bin\0" \
|
||||||
"update=" \
|
"update=" \
|
||||||
"protect off " xstr(BOOTFLASH_START) " +${filesize} && "\
|
"protect off " xstr(BOOTFLASH_START) " +${filesize} && "\
|
||||||
"erase " xstr(BOOTFLASH_START) " +${filesize} && " \
|
"erase " xstr(BOOTFLASH_START) " +${filesize} && " \
|
||||||
|
|
|
@ -74,6 +74,7 @@
|
||||||
#define CONFIG_KM_DEF_ENV_CPU \
|
#define CONFIG_KM_DEF_ENV_CPU \
|
||||||
"boot=bootm ${load_addr_r} - -\0" \
|
"boot=bootm ${load_addr_r} - -\0" \
|
||||||
"cramfsloadfdt=true\0" \
|
"cramfsloadfdt=true\0" \
|
||||||
|
"u-boot="xstr(CONFIG_HOSTNAME) "/u-boot.kwb\0" \
|
||||||
CONFIG_KM_DEF_ENV_UPDATE \
|
CONFIG_KM_DEF_ENV_UPDATE \
|
||||||
""
|
""
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue