summaryrefslogtreecommitdiff
path: root/include/configs/harmony.h
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-05-16 06:21:00 +0000
committerAlbert ARIBAUD <albert.u.boot@aribaud.net>2012-07-07 14:07:18 +0200
commitbea2674ccde5a495710adef62ebd5a294752f59d (patch)
treefc251c6dd7f90d43e26dbe5884ada4d2b2975899 /include/configs/harmony.h
parent07a84b7b1905f5b7464ad5746507306733eae964 (diff)
downloadu-boot-imx-bea2674ccde5a495710adef62ebd5a294752f59d.zip
u-boot-imx-bea2674ccde5a495710adef62ebd5a294752f59d.tar.gz
u-boot-imx-bea2674ccde5a495710adef62ebd5a294752f59d.tar.bz2
tegra: flesh out bootcmd
This implements a useful bootcmd for Tegra. The boot order is: * If USB enabled, USB storage * Internal MMC (SD card or eMMC) * If networking is enabled, BOOTP/TFTP When booting from USB or MMC, the boot script is assumed to be in partition 1 (although this may be overridden via the rootpart variable), both ext2 and FAT filesystems are supported, the boot script may exist in either / or /boot, and the boot script may be named boot.scr.uimg or boot.scr. When booting over the network, it is assumed that boot.scr.uimg exists on the TFTP server. There is less flexibility here since those setting up network booting are expected to need less hand-holding. In all cases, it is expected that the initial file loaded is a U-Boot image containing a script that will load the kernel, load any required initrd, load any required DTB, and finally bootm the kernel. Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'include/configs/harmony.h')
-rw-r--r--include/configs/harmony.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/include/configs/harmony.h b/include/configs/harmony.h
index 3706a40..25d6ec7 100644
--- a/include/configs/harmony.h
+++ b/include/configs/harmony.h
@@ -60,4 +60,7 @@
/* Environment not stored */
#define CONFIG_ENV_IS_NOWHERE
+
+#include "tegra2-common-post.h"
+
#endif /* __CONFIG_H */