Patchwork [U-Boot,2/4] Tegra: Medcom-Wide: Enable NAND and boot script support

login
register
mail settings
Submitter Thierry Reding
Date Feb. 14, 2013, 7:54 a.m.
Message ID <1360828494-16207-2-git-send-email-thierry.reding@avionic-design.de>
Download mbox | patch
Permalink /patch/220387/
State Changes Requested
Delegated to: Tom Warren
Headers show

Comments

Thierry Reding - Feb. 14, 2013, 7:54 a.m.
Boot script support brings Medcom-Wide in line with other Tegra boards.
In order to enable booting a Linux kernel with initial ramdisk, also add
support for the new FIT image type.

Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
---
 include/configs/medcom-wide.h | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)
Stephen Warren - Feb. 14, 2013, 5:19 p.m.
On 02/14/2013 12:54 AM, Thierry Reding wrote:
> Boot script support brings Medcom-Wide in line with other Tegra boards.
> In order to enable booting a Linux kernel with initial ramdisk, also add
> support for the new FIT image type.

I don't care if you enable FIT on your boards, but I would like to point
out that there's no requirement to enable FIT just to support ramdisks.
bootz/bootm support separate files/locations/... for ramdisks if you
want, and I'm pretty sure I validated it worked once at least.
Thierry Reding - Feb. 14, 2013, 7:23 p.m.
On Thu, Feb 14, 2013 at 10:19:28AM -0700, Stephen Warren wrote:
> On 02/14/2013 12:54 AM, Thierry Reding wrote:
> > Boot script support brings Medcom-Wide in line with other Tegra boards.
> > In order to enable booting a Linux kernel with initial ramdisk, also add
> > support for the new FIT image type.
> 
> I don't care if you enable FIT on your boards, but I would like to point
> out that there's no requirement to enable FIT just to support ramdisks.
> bootz/bootm support separate files/locations/... for ramdisks if you
> want, and I'm pretty sure I validated it worked once at least.

Yes, I seem to remember using that as well at some point. In most of our
products we ship a single uImage, though, which contains both the zImage
and the initrd.gz (when we can support all features on mainline, a DTB
will also be part of the same uImage). The main reason why we do this is
because it reduces the number of files that need to be distributed.

Thierry

Patch

diff --git a/include/configs/medcom-wide.h b/include/configs/medcom-wide.h
index bae4ba0..ea8e83f 100644
--- a/include/configs/medcom-wide.h
+++ b/include/configs/medcom-wide.h
@@ -44,14 +44,29 @@ 
 #define CONFIG_BOARD_EARLY_INIT_F
 #define CONFIG_BOARD_LATE_INIT
 
-#define CONFIG_ENV_IS_NOWHERE
-
 /* SD/MMC */
 #define CONFIG_MMC
 #define CONFIG_GENERIC_MMC
 #define CONFIG_TEGRA_MMC
 #define CONFIG_CMD_MMC
 
+#define CONFIG_DOS_PARTITION
+#define CONFIG_EFI_PARTITION
+#define CONFIG_FS_EXT4
+#define CONFIG_FS_FAT
+#define CONFIG_CMD_EXT2
+#define CONFIG_CMD_FAT
+#define CONFIG_CMD_FS_GENERIC
+
+/* NAND support */
+#define CONFIG_CMD_NAND
+#define CONFIG_TEGRA_NAND
+#define CONFIG_SYS_MAX_NAND_DEVICE	1
+
+/* Environment in NAND, aligned to start of last sector */
+#define CONFIG_ENV_IS_IN_NAND
+#define CONFIG_ENV_OFFSET		(SZ_512M - SZ_128K) /* 128K sectors */
+
 /* USB host support */
 #define CONFIG_USB_EHCI
 #define CONFIG_USB_EHCI_TEGRA
@@ -66,18 +81,6 @@ 
 #define CONFIG_CMD_NET
 #define CONFIG_CMD_DHCP
 
-#define CONFIG_DOS_PARTITION
-#define CONFIG_EFI_PARTITION
-#define CONFIG_CMD_EXT2
-#define CONFIG_CMD_FAT
-
-#define CONFIG_FIT
-
-#define CONFIG_BOOTCOMMAND				\
-	"mmc rescan;"					\
-	"ext2load mmc 0 0x17000000 /boot/uImage;"	\
-	"bootm"
-
 /* LCD support */
 #define CONFIG_LCD
 #define CONFIG_PWM_TEGRA
@@ -85,6 +88,9 @@ 
 #define LCD_BPP LCD_COLOR16
 #define CONFIG_SYS_WHITE_ON_BLACK
 
+/* support the new (FDT-based) image format */
+#define CONFIG_FIT
+
 #include "tegra-common-post.h"
 
 #endif /* __CONFIG_H */