This rule catches images such as MLO.byteswap
Signed-off-by: NJustin Waters <justin.waters@timesys.com>

The BeagleBone Black can boot from either the MMC card
or eMMC chip on board. We should try both interfaces.

This modification also allows a graceful fallback if
a device exists but boot images are not present on it.

Changes for v2:

* Fix boot partition - it should always show up as mmcblk0p2
* Fix missing FDT load
Signed-off-by: NJustin Waters <justin.waters@timesys.com>

Many modern U-Boot ports enable command line editing and
a history buffer. The am335x_evm configuration is fairly
comprehensive as it is, so a few extra kb should not be
noticable, and it adds a very convenient feature.
Signed-off-by: NJustin Waters <justin.waters@timesys.com>

Give the user the ability to disable NAND support by defining
CONFIG_NO_NAND. This will allow custom hardware to easily support
this configuration.
Signed-off-by: NJustin Waters <justin.waters@timesys.com>
[trini: Make apply on top of other series]
Signed-off-by: NTom Rini <trini@ti.com>

accessing a lan9303 switch with the cpsw driver results in wrong
speed detection, as the switch sets the BMSR_ERCAP in BMSR
register, and follow read of the MII_STAT1000 register fails, as
the switch does not support it. Current code did not check,
if a phy_read() fails ... fix this.
Signed-off-by: NHeiko Schocher <hs@denx.de>
Cc: Joe Hershberger <joe.hershberger@gmail.com>
Acked-by: NMugunthan V N <mugunthanvnm@ti.com>
Signed-off-by: NTom Rini <trini@ti.com>

The Beaglebone White may be populated with a memory cape that has a NOR
module.  Document how to program it.
Signed-off-by: NTom Rini <trini@ti.com>

NOR requires that s_init be within the first 4KiB of the image so that
we can perform the rest of the required pinmuxing to talk with the rest
of NOR that we are found on.  When NOR_BOOT is set we save our
environment in NOR at 512KiB and a redundant copy at 768KiB.  We avoid
using SPL for this case and u-boot.bin is written directly to the start
of NOR.

We enclose the DMM-related parts of arch/arm/cpu/armv7/am33xx/emif4.c
with TI81xx checks as at this time U-Boot does not discard unused
sections in the main build and this code relies on functions specific to
(and only provided in) ti81xx-related code.

Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
Signed-off-by: NSteve Kipisz <s-kipisz2@ti.com>
Signed-off-by: NTom Rini <trini@ti.com>

This patch adds support for the NOR module that attaches
to the memory cape for a Beaglebone board. This does not
add booting support; only support so that you can boot from
SD/MMC and see the NOR module so that it can be programmed.
Signed-off-by: NSteve Kipisz <s-kipisz2@ti.com>
[trini: Clean up config changes slightly]
Signed-off-by: NTom Rini <trini@ti.com>

Based on our usage of the GPMC, either with NOR or NAND we do not need
to be setting the irqstatus or irqenable bits and should clear them like
we have historically.
Signed-off-by: NTom Rini <trini@ti.com>

We rework the various board_is_foo() checks to take a pointer to
struct am335x_baseboard_id rather than using a local copy in board.c.
This allows us to make use of the same checks in mux.c as well as fixing
problems when this code could be running from read-only memory.
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: NTom Rini <trini@ti.com>

- Style cleanup (# define -> #define)
- Due to ROM issues, redudant loading isn't feasible, so drop.
- Given extra space, increase max size of U-Boot to 512KiB
- Correct env size to match usage (we had not re-defined ENV_SIZE).
- Given extra space, keep env size as 128KiB, add redundant environment.
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: NTom Rini <trini@ti.com>

We always set a CONFIG_ENV_IS_...somewhere... so drop the initial define
of NOWHERE.
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: NTom Rini <trini@ti.com>

The AM335x GP EVM ships with NAND.  Document programming of the chip
including the redundant locations that the ROM will check.
Signed-off-by: NTom Rini <trini@ti.com>

If no other bootoption works, try loading up device tree and zImage.

This is selected as the last option to allow backward compatibility as
well as support the recent trend in moving kernel boot to using zImage
and device tree.

NOTE: if uImage is present in bootpart, it will try this first and
will assume this is to be booted with bootm (so may be concatenated
image or plain vanilla ATAG MACHINE_ID based image)
Signed-off-by: NNishanth Menon <nm@ti.com>

For folks not using concatenated device tree with uImage, having
an handy function to find and load device tree is very handy.

So introduce findfdt and loadfdt and run findfdt by default to make
it easier on user scripts.
Signed-off-by: NNishanth Menon <nm@ti.com>

CMD_FS_GENERIC allows us to simplify where we load up our image from
either from ext2/fat etc. So, lets use that instead of cumbersome
options we currently use. Sticking with existing conventions,
defaults will be:
ramdisk=ramdisk.gz
bootpart=0:2 (second partition)
bootdir=/boot (/boot in second partition)

This matches with the default behavior, these can be overriden by
env files as needed.
Signed-off-by: NNishanth Menon <nm@ti.com>

As reported in http://marc.info/?l=u-boot&m=137358037827735&w=2

There is no need for the "xMB" variant, as the gpio pins used for
identification where never changed from the xMA when the newer silcon
was used for the xMB, So rename XM A revision as AB revision
and report accordingly
Reported-by: NRobert Nelson <robertcnelson@gmail.com>
Signed-off-by: NNishanth Menon <nm@ti.com>

e6829308
(BeagleBoard: config: use uImage.beagle for tftp)

Introduced uImage.beagle which does not happen to be default output
file of Linux kernel build make uImage (output is uImage).

So, replace uImage.beagle with uImage
Signed-off-by: NNishanth Menon <nm@ti.com>

We do not use JFFS2 by default and it conflicts with
CONFIG_CMD_FS_GENERIC (ls command is the same). Since most of our
BOOTCMD can be simplified by using the FS_GENERIC, dropping JFFS2
Signed-off-by: NNishanth Menon <nm@ti.com>
Acked-by: NJoel Fernandes <joelf@ti.com>

Enabling CPSW Ethernet support in DRA7xx EVM.
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Adding CPSW Slave 0 and MDIO pinmux support for DRA7xx EVM
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Adding support for CPSW Ethernet support found in DRA7xx EVM
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Enabling CPSW module by enabling GMAC clock control
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Locking DPLL_GMAC

[mugunthanvnm@ti.com:Configure only if CPSW is selected]
Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Enable hardware statistics for all ports, enabling only to host port is useless
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

BD ram address may vary in various SOC, so removing the hardcoding and
passing the same information through platform data
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>

Add a README for the family of boards the am335x_evm covers, and include
instructions on preparing and using falcon mode, for various media.
Signed-off-by: NTom Rini <trini@ti.com>
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>
Reviewed-by: NLukasz Majewski <l.majewski@samsung.com>

We use CONFIG_CMD_SPL_WRITE_SIZE when reading/writing the args portion
of falcon mode to NAND.  Previously it was half the size of the
eraseblock which is too small, increase to eraseblock size.
Signed-off-by: NTom Rini <trini@ti.com>

The previous location used for the "args" portion of falcon mode was too
small to allow for a device tree to be saved there, so move the location
slightly and increase the size.  In addition, our previous kernel
location was part of the area we set aside for U-Boot itself, so move it
up a bit higher.
Signed-off-by: NTom Rini <trini@ti.com>
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>

Now that we have falcon mode enabled, the partiton numbers for NAND have
changed, and we need to list entries for updating these parts of the
system.  While adding falcon mode entires for eMMC (raw), we round up
the limit on U-Boot for ease of math later.
Signed-off-by: NTom Rini <trini@ti.com>
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>

Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: NTom Rini <trini@ti.com>

The OMAP36xx/OMAP37xx family uses L3 frequency of 200MHz instead of 165MHz
used by OMAP34xx/OMAP35xx.

Also fix checkpatch warning about alignment.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>

Currently, we assume that if we can read from MMC correctly, we have
found a valid image.  This is not the case as an empty area will read
just fine.  Add a check for a valid IH_MAGIC.
Signed-off-by: NTom Rini <trini@ti.com>
Reviewed-by: NPeter Korsgaard <jacmet@sunsite.dk>

The current code uses clrbits_be32 which is incorrect since we are on
a little endian machine here. This patch fixes this issue and also removes
some unnecessary code: Reading the current GPIO bank state is not required
if we are using the SET and CLEAR GPIO registers for setting/clearing
bits.
Signed-off-by: NChristian Riesch <christian.riesch@omicron.at>
Cc: Nagabhushana Netagunte <nagabhushana.netagunte@ti.com>
Cc: Rajashekhara, Sudhakar <sudhakar.raj@ti.com>

Currently in OMAP3 SPL, the GPMC for NAND is configured for 16bit
access. This patch adds support for 8bit NAND devices as well.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Tom Rini <trini@ti.com>

Signed-off-by: NTom Rini <trini@ti.com>

Conflict over SPDX changes means that one change was effectively dropped
as it was fixing typos in a removed hunk of text.

Conflicts:
	arch/mips/cpu/mips64/start.S
Signed-off-by: NTom Rini <trini@ti.com>

Acked-by: NHeiko Schocher <hs@denx.de>
Signed-off-by: NTom Rini <trini@ti.com>