24 Jul, 2013
2 commits
-
The sandburst-specific i2c drivers have been deleted, conflict was just
over the SPDX conversion.Conflicts:
board/sandburst/common/ppc440gx_i2c.c
board/sandburst/common/ppc440gx_i2c.hSigned-off-by: Tom Rini
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
23 Jul, 2013
1 commit
-
This enables CONFIG_SYS_I2C on Tegra, updating existing boards and the Tegra
i2c driver to support this.Signed-off-by: Simon Glass
Signed-off-by: Heiko Schocher
14 Jun, 2013
1 commit
-
Use a negative value of CONFIG_ENV_OFFSET for all NVIDIA reference boards
that store the U-Boot environment in the 2nd eMMC boot partition. This
makes U-Boot agnostic to the size of the eMMC boot partition, which can
vary depending on which eMMC device was actually stuffed into the board.Signed-off-by: Stephen Warren
Acked-by: Tom Warren
Signed-off-by: Andy Fleming
15 Mar, 2013
1 commit
-
Enable a common set of partition types, filesystems, and related
commands in tegra-common.h, so that they are available on all Tegra
boards. This allows boot.scr (loaded and executed by the default
built-in environment) on those boards to assume that certain features
are always available.Do this in tegra-common.h, so that individual board files can undefine
the features if they really don't want any of them.Signed-off-by: Stephen Warren
Acked-by: Simon Glass
Signed-off-by: Tom Warren
19 Nov, 2012
1 commit
-
Modify tegra-common-post.h's BOOTCOMMAND definition to use the generic
filesystem command load rather than separate fatload and ext2load.
This removes the need to iterate over supported filesystem types in the
boot command.This requires editing all board config headers to enable the new
commands. The now-unused commands are left enabled to assue backwards
compatibility with any user scripts. Boards (all from Avionic Design)
which define custom BOOTCOMMAND values are not affected.Signed-off-by: Stephen Warren
tegra generic fs cmds fixup
Signed-off-by: Tom Warren
16 Oct, 2012
1 commit
-
Remove any notion of CONFIG_SERIAL_MULTI from board config files.
Since CONFIG_SERIAL_MULTI is now enabled by default, it is useless
to specify this config option in the board config files. Therefore
remove it.Signed-off-by: Marek Vasut
Cc: Marek Vasut
Cc: Anatolij Gustschin
Cc: Stefan Roese
Signed-off-by: Tom Rini
11 Sep, 2012
1 commit
-
Convert TEGRA20_ defines to either TEGRA_ or NV_PA_ where appropriate.
Convert tegra20_ source file and function names to tegra_, also.Upcoming Tegra30 port will use common code/defines/names where possible.
Signed-off-by: Tom Warren
Acked-by: Stephen Warren
08 Sep, 2012
1 commit
-
When I set up Tegra's config files to put the environment into eMMC, I
assumed that CONFIG_ENV_OFFSET was a linearized address relative to the
start of the eMMC device, and spanning HW partitions boot0, boot1,
general* and the user area in order. However, it turns out that the
offset is actually relative to the beginning of the user area. Hence,
the environment block ended up in a different location to expected and
documented.Set CONFIG_SYS_MMC_ENV_PART=2 (boot1) to solve this, and adjust
CONFIG_ENV_OFFSET to be relative to the start of boot1, not the entire
eMMC.Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren
01 Sep, 2012
1 commit
-
This is make naming consistent with the kernel and devicetree and in
preparation of pulling out the common tegra20 code.Signed-off-by: Allen Martin
Acked-by: Stephen Warren
Tested-by: Thierry Reding
Signed-off-by: Tom Warren
07 Jul, 2012
8 commits
-
Walk the BIT and BCT to find the ODMDATA word in the
CustomerData field and put it into Scratch20 reg for
use by kernel, etc.Built all Tegra builds OK; Booted on Seaboard and saw
ODMDATA in PMC scratch20 was the same as the value in my
burn-u-boot.sh file (0x300D8011). NOTE: All flash utilities
will have to specify the odmdata (nvflash --odmdata n) on
the command line or via a cfg file, or built in to their
BCT.Signed-off-by: Tom Warren
Acked-by: Stephen Warren -
In anticipation of Tegra3 support, continue removing/renaming
Tegra2-specific files. No functional changes (yet).
Updated copyrights to 2012.Signed-off-by: Tom Warren
-
Store the environment in eMMC, at the end of the second boot sector.
This should not conflict with any other eMMC usage: U-Boot is stored
well below this location, and the kernel only uses the general area
of the eMMC once booted, not the boot sectors.Note: This assumes the user plugged the standard 8MB MoviNAND card into
J29/HSMMC/POP. If they didn't, the boot sector layout may be different.
However, use of that particular card is standard practice as far as I
know.Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren -
The SMSC95xx series may exist either directly on a main board, or as a USB
to Ethernet dongle. However, dongles containing these chips are very rare.
Hence, remove this config option, except on Harmony where such a chip is
actually present on the board.The asix option remains, since it's a popular chip, and I actively use a
dongle containing this.Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren
Acked-by: Igor Grinberg -
CONFIG_CMD_PING/NFS aren't required for Whistler to boot.
Add some comments.
Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren -
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/TFTPWhen 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
Signed-off-by: Tom Warren -
console isn't used by anything, and the kernel should be set appropriately
by whatever script is booting the kernel, not imposed by the bootloader.mem might be useful, but the current value is pretty bogus, since it
includes nvmem options that make no sense for an upstream kernel, and
equally should not be required for any downstream kernel. Either way, this
is also best left to the kernel boot script.smpflag isn't used by anything, and again was probably intended to be a
kernel command-line option better set by the kernel boot script.Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren -
Whistler is a highly configurable Tegra evaluation and development board.
This change adds support for the following specific configuration:E1120 motherboard
E1108 CPU board
E1116 PMU boardThe motherboard configuration switches are set as follows:
SW1=0 SW2=0 SW3=5
S1/S2/S3/S4 all on, except S3 7/8 are off.Other combinations of daugher boards may work to varying degrees, but will
likely require some SW adjustment.Signed-off-by: Stephen Warren
Signed-off-by: Tom Warren
