Skip to contentSkip to conversation

mpc83xx: mpc8349itx - accommodate larger kernel sizes & unzero the bootdelay

PATCH New Kim Phillips 1 participant 2 messages Aug 24, 2009 – Aug 27, 2009

lore
Share & tools
lore

Kim Phillips

author
#0 lore raw

PATCH 1/1 mpc83xx: mpc8349itx - accommodate larger kernel sizes & unzero the bootdelay

apparently the ITX was missed last round.

Also make bootdelay consistent with other boards, so as to give on the opportunity to fix mistakenly set bootcmd without having checked for an bootdelay zero setting first.

Signed-off-by Kim Phillips <[email protected]>
---
 include/configs/MPC8349ITX.h |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
include/configs/MPC8349ITX.h +3 -3
index fd5ad70..3b4e344 100644
@@ -515,7 +515,7 @@ boards, we say we have two, but don't display a message if we find only one. */
 #define CONFIG_SYS_PROMPT_HUSH_PS2 "> "
 
 #define CONFIG_SYS_LOAD_ADDR	0x2000000	/* default load address */
-#define CONFIG_LOADADDR	500000	/* default location for tftp and bootm */
+#define CONFIG_LOADADDR	800000	/* default location for tftp and bootm */
 
 #ifdef CONFIG_MPC8349ITX
 #define CONFIG_SYS_PROMPT	"MPC8349E-mITX> "	/* Monitor Command Prompt */

@@ -708,7 +708,7 @@ boards, we say we have two, but don't display a message if we find only one. */
 #define CONFIG_FDTFILE		mpc8349emitxgp.dtb
 #endif
 
-#define CONFIG_BOOTDELAY	0
+#define CONFIG_BOOTDELAY	6
 
 #define XMK_STR(x)	#x
 #define MK_STR(x)	XMK_STR(x)

@@ -731,7 +731,7 @@ boards, we say we have two, but don't display a message if we find only one. */
 		"cp.b $loadaddr " MK_STR(TEXT_BASE) " $filesize; "	\
 		"protect on " MK_STR(TEXT_BASE) " +$filesize; "		\
 		"cmp.b $loadaddr " MK_STR(TEXT_BASE) " $filesize\0"	\
-	"fdtaddr=400000\0"						\
+	"fdtaddr=780000\0"						\
 	"fdtfile=" MK_STR(CONFIG_FDTFILE) "\0"
 
 #define CONFIG_NFSBOOTCOMMAND						\
Signature · 1 line
1.6.4
author Applied
#1 lore raw

PATCH 1/1 mpc83xx: mpc8349itx - accommodate larger kernel sizes & unzero the bootdelay

Quoted 8 lines · On Mon, 24 Aug 2009 14:32:18 -0500 Kim Phillips <[email protected]>…

apparently the ITX was missed last round.

Also make bootdelay consistent with other boards, so as to give on the opportunity to fix mistakenly set bootcmd without having checked for an bootdelay zero setting first.

Signed-off-by Kim Phillips <[email protected]>

---

applied.

Kim