|
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ */
|
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>
12 years ago
|
|
|
/*
|
|
|
|
|
* (C) Copyright 2010-2012
|
|
|
|
|
* NVIDIA Corporation <www.nvidia.com>
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __TEGRA_COMMON_POST_H
|
|
|
|
|
#define __TEGRA_COMMON_POST_H
|
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>
12 years ago
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Size of malloc() pool
|
|
|
|
|
*/
|
|
|
|
|
#ifdef CONFIG_DFU_OVER_USB
|
|
|
|
|
#define CONFIG_SYS_MALLOC_LEN (SZ_4M + \
|
|
|
|
|
CONFIG_SYS_DFU_DATA_BUF_SIZE + \
|
|
|
|
|
CONFIG_SYS_DFU_MAX_FILE_SIZE)
|
|
|
|
|
#else
|
|
|
|
|
#define CONFIG_SYS_MALLOC_LEN (4 << 20) /* 4MB */
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#define CONFIG_SYS_NONCACHED_MEMORY (1 << 20) /* 1 MiB */
|
|
|
|
|
|
|
|
|
|
#ifndef CONFIG_SPL_BUILD
|
|
|
|
|
#define BOOT_TARGET_DEVICES(func) \
|
|
|
|
|
func(MMC, mmc, 1) \
|
|
|
|
|
func(MMC, mmc, 0) \
|
|
|
|
|
func(USB, usb, 0) \
|
|
|
|
|
func(PXE, pxe, na) \
|
|
|
|
|
func(DHCP, dhcp, na)
|
|
|
|
|
#include <config_distro_bootcmd.h>
|
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>
12 years ago
|
|
|
#else
|
|
|
|
|
#define BOOTENV
|
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>
12 years ago
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_TEGRA_KEYBOARD
|
|
|
|
|
#define STDIN_KBD_KBC ",tegra-kbc"
|
|
|
|
|
#else
|
|
|
|
|
#define STDIN_KBD_KBC ""
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_USB_KEYBOARD
|
|
|
|
|
#define STDIN_KBD_USB ",usbkbd"
|
|
|
|
|
#define CONFIG_PREBOOT "usb start"
|
|
|
|
|
#else
|
|
|
|
|
#define STDIN_KBD_USB ""
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_LCD
|
|
|
|
|
#define STDOUT_LCD ",lcd"
|
|
|
|
|
#else
|
|
|
|
|
#define STDOUT_LCD ""
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_DM_VIDEO
|
|
|
|
|
#define STDOUT_VIDEO ",vidconsole"
|
|
|
|
|
#else
|
|
|
|
|
#define STDOUT_VIDEO ""
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_CROS_EC_KEYB
|
|
|
|
|
#define STDOUT_CROS_EC ",cros-ec-keyb"
|
|
|
|
|
#else
|
|
|
|
|
#define STDOUT_CROS_EC ""
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#define TEGRA_DEVICE_SETTINGS \
|
|
|
|
|
"stdin=serial" STDIN_KBD_KBC STDIN_KBD_USB STDOUT_CROS_EC "\0" \
|
|
|
|
|
"stdout=serial" STDOUT_LCD STDOUT_VIDEO "\0" \
|
|
|
|
|
"stderr=serial" STDOUT_LCD STDOUT_VIDEO "\0" \
|
|
|
|
|
""
|
|
|
|
|
|
|
|
|
|
#ifndef BOARD_EXTRA_ENV_SETTINGS
|
|
|
|
|
#define BOARD_EXTRA_ENV_SETTINGS
|
|
|
|
|
#endif
|
|
|
|
|
|
ARM: tegra: CONFIG_{SYS_, }LOAD{_, }ADDR rationalization
As best I can tell, CONFIG_SYS_LOAD_ADDR and CONFIG_LOADADDR/$loadaddr
serve essentially the same purpose. Roughly, if a command takes a load
address, then CONFIG_SYS_LOAD_ADDR or $loadaddr (or both) are the default
if the command-line does not specify the address. Different U-Boot
commands are inconsistent re: which of the two default values they use.
As such, set the two to the same value, and move the logic that does this
into tegra-common-post.h so it's not duplicated. A number of other non-
Tegra boards do this too.
The values chosen for these macros are no longer consistent with anything
in MEM_LAYOUT_ENV_SETTINGS. Regain consistency by setting $kernel_addr_r
to CONFIG_LOADADDR. Older scripts tend to use $loadaddr for the default
kernel load address, whereas newer scripts and features tend to use
$kernel_addr_r, along with other variables for other purposes such as
DTBs and initrds. Hence, it's logical they should share the same value.
I had originally thought to make the $kernel_addr_r and CONFIG_LOADADDR
have different values. This would guarantee no interference if a script
used the two variables for different purposes. However, that scenario is
unlikely given the semantic meaning associated with the two variables.
The lowest available value is 0x90200000; see comments for
MEM_LAYOUT_ENV_SETTINGS in tegra30-common-post.h for details. However,
that value would be problematic for a script that loaded a raw zImage to
$loadaddr, since it's more than 128MB beyond the start of SDRAM, which
would interfere with the kernel's CONFIG_AUTO_ZRELADDR. So, let's not do
that.
The only potential fallout I could foresee from this patch is if someone
has a script that loads the kernel to $loadaddr, but some other file
(DTB, initrd) to a hard-coded address that the new value of $loadaddr
interferes with. This seems unlikely. A user should not do that; they
should either hard-code all load addresses, or use U-Boot-supplied
variables for all load addresses. Equally, any fallout due to this change
is trivial to fix; simply modify the load addresses in that script.
Cc: Paul Walmsley <pwalmsley@nvidia.com>
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Paul Walmsley <pwalmsley@nvidia.com>
Reviewed-by: Simon Glass
Signed-off-by: Tom Warren <twarren@nvidia.com>
9 years ago
|
|
|
#define CONFIG_SYS_LOAD_ADDR CONFIG_LOADADDR
|
|
|
|
|
|
|
|
|
|
#ifndef CONFIG_CHROMEOS_EXTRA_ENV_SETTINGS
|
|
|
|
|
#define CONFIG_CHROMEOS_EXTRA_ENV_SETTINGS
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_ARM64
|
|
|
|
|
#define FDT_HIGH "ffffffffffffffff"
|
|
|
|
|
#define INITRD_HIGH "ffffffffffffffff"
|
|
|
|
|
#else
|
|
|
|
|
#define FDT_HIGH "ffffffff"
|
|
|
|
|
#define INITRD_HIGH "ffffffff"
|
|
|
|
|
#endif
|
|
|
|
|
|
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>
12 years ago
|
|
|
#define CONFIG_EXTRA_ENV_SETTINGS \
|
|
|
|
|
TEGRA_DEVICE_SETTINGS \
|
|
|
|
|
MEM_LAYOUT_ENV_SETTINGS \
|
|
|
|
|
"fdt_high=" FDT_HIGH "\0" \
|
|
|
|
|
"initrd_high=" INITRD_HIGH "\0" \
|
|
|
|
|
BOOTENV \
|
|
|
|
|
BOARD_EXTRA_ENV_SETTINGS \
|
|
|
|
|
CONFIG_CHROMEOS_EXTRA_ENV_SETTINGS
|
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>
12 years ago
|
|
|
|
|
|
|
|
#if defined(CONFIG_TEGRA20_SFLASH) || defined(CONFIG_TEGRA20_SLINK) || defined(CONFIG_TEGRA114_SPI)
|
|
|
|
|
#define CONFIG_TEGRA_SPI
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/* overrides for SPL build here */
|
|
|
|
|
#ifdef CONFIG_SPL_BUILD
|
|
|
|
|
|
|
|
|
|
#define CONFIG_SKIP_LOWLEVEL_INIT_ONLY
|
|
|
|
|
|
|
|
|
|
/* remove I2C support */
|
|
|
|
|
#ifdef CONFIG_SYS_I2C_TEGRA
|
|
|
|
|
#undef CONFIG_SYS_I2C_TEGRA
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/* remove USB */
|
|
|
|
|
#ifdef CONFIG_USB_EHCI_TEGRA
|
|
|
|
|
#undef CONFIG_USB_EHCI_TEGRA
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#endif /* CONFIG_SPL_BUILD */
|
|
|
|
|
|
|
|
|
|
#endif /* __TEGRA_COMMON_POST_H */
|
