The change is currently needed to be able to remove the board
configuration scripting from the top level Makefile and replace it by
a simple, table driven script.

Moving this configuration setting into the "CONFIG_*" name space is
also desirable because it is needed if we ever should move forward to
a Kconfig driven configuration system.
Signed-off-by: NWolfgang Denk <wd@denx.de>

When planning for more generalization and Makefile cleanup it became
obvious that the introduction of a separate CONFIG_MK_ name space for
config options that were set through scripting in the Makefile was
not a good idea.

Originally the idea was to provide a script-free approach to supply
configuration options - there was no real need for a separate name
space. But when we now convert the existing Makefile entries to make
use of this approach, it would mean that we have to touch a large
number of board config files and add #ifdef / #define sequences to
"convert" from the CONFIG_MK_ to the CONFIG_ name space.

It seems much cleaner to get rid of this somewhat arbitrary _MK
string now for the few boards that actually use it.
Signed-off-by: NWolfgang Denk <wd@denx.de>
Acked-by: NMike Frysinger <vapier@gentoo.org>

The logodl board has long been unmaintained and left broken.
As obviously nobody is interestedin that code any more, we may as well
remove it.
Signed-off-by: NWolfgang Denk <wd@denx.de>
Cc: August Hoeraendl <august.hoerandl@gmx.at>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Marek Vasut <marek.vasut@gmail.com>

commit 6d014adf dropped support for the forceenv() function, but failed
to remove references to it from board/davinci/schmoogie/schmoogie.c

Replace forceenv() by setenv() and set CONFIG_ENV_OVERWRITE instead in
the board config file to allow overwriting the serial number.
Signed-off-by: NWolfgang Denk <wd@denx.de>
Cc: Sergey Kubushyn <ksi@koi8.net>
Acked-by: NSergey Kubushyn <ksi@koi8.net>

This patch fixes the LINUX_BOOT_PARAM_ADDR define to be based off of
PHYS_SDRAM_1 instead of CONFIG_SYS_MEMTEST_START. On da830 they are the same
thing but on da850 the CONFIG_SYS_MEMSTART define is offset from the
PHYS_SDRAM_1 start.

Without this patch it is not possible to boot linux on da850 -- bootm hangs
at "Uncompressing Linux... done, booting the kernel."
Signed-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

The current da850evm support in u-boot/master omits any use of
the davinci EMAC. This patch adds basic support for the EMAC using
the MII PHY found on the baseboard of the EVM. The MAC address is
read from the environment variable 'ethadd'. Note that this is
different from the da850evm support in the u-boot omapl1 tree
where the MAC address is read from SPI flash.
Signed-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
CC: Sandeep Paulraj <s-paulraj@ti.com>
CC: Sudhakar Rajashekhara <sudhakar.raj@ti.com>
CC: Ben Warren <biggerbadderben@gmail.com>
CC: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

This patch enables also the mtdpart, ubi and ubifs commands when NAND support
is enabled.

Signed-off-by: Ben Gardiner<bengardiner@nanometrics.ca>
To: Sudhakar Rajashekhara <sudhakar.raj@ti.com>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

The current da850evm config is missing the pieces for NAND support that can be
found in Sandeep's u-boot-davinci tree [1].

This patch adds NAND support in the spirit of the support in the u-boot-davinci
tree where NAND support for the da850evm can be enabled by putting a single
'#define CONFIG_USE_NAND' at the top of the include/configs/da850evm.h file.

[1] http://arago-project.org/git/people/?p=sandeep/u-boot-davinci.git;a=treeSigned-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

The IGEP module is a low-power, high performance production-ready
system-on-module (SOM) based on TI's OMAP3 family.The IGEP module
solution based upon TI OMAP3 provides a low-power/low-cost platform
for a variety of consumer/industrial/medical devices.
Signed-off-by: NEnric Balletbo i Serra <eballetbo@gmail.com>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

The IGEP v2 board is a low-cost, fan-less and industrial temperature
range single board computer that unleashes laptop-like performance and
expandability without the bulk, expense, or noise of typical desktop
machines. Its architecture shares much in common with other OMAP3 boards.
Signed-off-by: NEnric Balletbo i Serra <eballetbo@gmail.com>
Acked-by: NSteve Sakoman <steve.sakoman@linaro.org>
Tested-by: NSteve Sakoman <steve.sakoman@linaro.org>
Signed-off-by: NSandeep Paulraj <s-paulraj@ti.com>

This patch fixes the build breakage introduced by the recent relocation
changes for ARMV7
Signed-off-by: NSteve Sakoman <steve@sakoman.com>

Signed-off-by: NSteve Sakoman <steve@sakoman.com>

This patch fixes the build breakage introduced by the recent relocation
changes for ARMV7
Signed-off-by: NSteve Sakoman <steve@sakoman.com>

The SDP4430 does not have onboard NAND, it has eMMC on the second
MMC slot.  This patch adds support for saving the u-boot environment
to eMMC.
Signed-off-by: NAneesh V <aneesh@ti.com>
Signed-off-by: NSukumar Ghorai <s-ghorai@ti.com>
Tested-by: NSteve Sakoman <steve@sakoman.com>

This patch switches from the legacy mmc driver to the new generic mmc driver
Signed-off-by: NSteve Sakoman <steve@sakoman.com>

This patch switches from the legacy mmc driver to the new generic mmc driver
Signed-off-by: NSteve Sakoman <steve@sakoman.com>

This patch switches from the legacy mmc driver to the new generic mmc driver
Signed-off-by: NSukumar Ghorai <s-ghorai@ti.com>
Tested-by: NSteve Sakoman <steve@sakoman.com>

This patch switches from the legacy mmc driver to the new generic mmc driver
Signed-off-by: NSukumar Ghorai <s-ghorai@ti.com>
Tested-by: NSteve Sakoman <steve@sakoman.com>

TI hasn't reserved a USB Product ID for gadgets, so use the default
vendor and product ID to avoid confusion.
Signed-off-by: NSteve Sakoman <steve@sakoman.com>

Only a few PPC boards actually use the common BAT manipulation
functions, so only compile it for them.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

Signed-off-by: NStefano Babic <sbabic@denx.de>

The patch adds the possibility to update the QONG
FPGA (a Lattice XP2-5E) with u-boot using some GPIOs
to drive the JTAG interface.
Signed-off-by: NStefano Babic <sbabic@denx.de>

Adds support for the ARM quad-core Cortex-A9 processor

This system includes a motherboard(Versatile Express), daughterboard
(Coretile), and SOC(Cortex-A9 quad core).  The serial port, ethernet,
and flash systems work with these additions.  The naming convention
is:
   SOC -> CortexA9 quad core = ca9x4
   daughterboard -> Coretile = ct
   motherboard -> Versatile Express = vxp
This gives ca9x4_ct_vxp.c as the board support file.
Signed-off-by: NMatt Waddel <matt.waddel@linaro.org>

Merge several sizes.h in asm/arch subdirectories into a single
asm/sizes.h file.

Fixup usage of asm/arch/sizes.h in some files to use the merged file.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>

There were some #undef's of CONFIG_SYS_ARM_WITHOUT_RELOC added to a few board
configs as part of the arm relocation series; but these are not needed now as we
do not #undef what is not #defined in the first place.
Signed-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
CC: Heiko Schocher <hs@denx.de>

Signed-off-by: NHeiko Schocher <hs@denx.de>

All Kirkwood based boards are supported for this new implementation
ref: docs/README.arm-relocation
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

It is observed that, in most of the board configs the code is being
duplicated, also for any common change all board files needs update
This issue was under discussion from long on mailing list and we
converge on introducing common config file.

With this patch-
1. Total Kirkwood specific configuration code is reduced by 210 lines
2. All common configuration can be shared by multiple boards
3. Easy to manage common updates like ARM relocation changes

mv-common.h file is added to include/configs/
It contains all common configuration supported for all Kirkwood boards
The respective board configs are updated for its usage

Build tested for guruplug, mv88f6281gtw_ge, openrd_base,
rd6281a and sheevaplug
Binary execution tested for sheevaplug

Todo:
1. Other custom Kirkwood boards to be synced
2. The support to be extended for Orion5X based boards
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

For all Kirkwood boards so far dram_init function is duplicated
dram_init function is moved to dram.c and relevant code from all
board specific files removed

If any board needs specific dram init handling than standard one,
then, a macro CONFIG_SYS_BOARD_DRAM_INIT should be defined in
board config header file and the dram_init function can be put
in board specific source file
For ex. keymile boards
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

This patch adds support for displaying boot progress codes on a4m072 board
using LED display. As we can display only one symbol at any time on the hardware
(two symbols with blinking) we can't display progress codes directly and have
to map them to 2-symbol codes.
We use the following mapping on the a4m972 board:
 [1, 8] U [100, 108]					-> 5
 [-9, -1] U [-101, -100] U [-113, -103]			-> -5
 [9, 14] U [120, 123] U [125, 129]			-> 8
 [-13, -10] U [-122, -120] U [-127, -124] U {-129}	-> -8
 {15}							-> 9
 [-32, -30]						-> -A
 [-40, -35] U [-51, -42] U [-58, -53] U
		[-83, -80] U {-64, -130, -140, -150}	-> -B

Other progress code are ignored. One symbol codes are displayed steady while
two-symbol codes are displayed using blinking. Boot progress codes are
displayed with decimal got unset (as opposed to 'display' command output).
Signed-off-by: NIlya Yanok <yanok@emcraft.com>

This patch adds support for LED display on a4m072 board. Hardware is
capable of displaying only one symbol at any time. We support displaying
two symbols in software (via blinking).
Signed-off-by: NIlya Yanok <yanok@emcraft.com>

Split the display command into generic interface and hardware-specific
realization for PDSP188x LED display found on hmi1001 and manroland
boards. Simple interface for LED displays is defined in
include/led-display.h and described in doc/README.LED_display.
Driver-specific implementation was moved into drivers/misc/pdsp188x.c
file (enabled with CONFIG_PDSP188x set).
Signed-off-by: NIlya Yanok <yanok@emcraft.com>

This patch provides support for the A4M072 board with the following features:
 UART
 NOR flash
 FEC Ethernet
 External SRAM
 I2C EEPROM
 CompactFlash cards on IDE/ATA port
 USB Host
 PCI initialization

The 7-segment LED indicator is not yet supported.
Signed-off-by: NSergei Poselenov <sposelenov@emcraft.com>

All Kirkwood based boards are supported for this new implementation
ref: docs/README.arm-relocation
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

It is observed that, in most of the board configs the code is being
duplicated, also for any common change all board files needs update
This issue was under discussion from long on mailing list and we
converge on introducing common config file.

With this patch-
1. Total Kirkwood specific configuration code is reduced by 210 lines
2. All common configuration can be shared by multiple boards
3. Easy to manage common updates like ARM relocation changes

mv-common.h file is added to include/configs/
It contains all common configuration supported for all Kirkwood boards
The respective board configs are updated for its usage

Build tested for guruplug, mv88f6281gtw_ge, openrd_base,
rd6281a and sheevaplug
Binary execution tested for sheevaplug

Todo:
1. Other custom Kirkwood boards to be synced
2. The support to be extended for Orion5X based boards
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

For all Kirkwood boards so far dram_init function is duplicated
dram_init function is moved to dram.c and relevant code from all
board specific files removed

If any board needs specific dram init handling than standard one,
then, a macro CONFIG_SYS_BOARD_DRAM_INIT should be defined in
board config header file and the dram_init function can be put
in board specific source file
For ex. keymile boards
Signed-off-by: NPrafulla Wadaskar <prafulla@marvell.com>

Microblaze hasn't supported NET_MULTI support.
Signed-off-by: NMichal Simek <monstr@monstr.eu>

1. Fix preprocessor statements
2. Clean coding style
Signed-off-by: NMichal Simek <monstr@monstr.eu>

Signed-off-by: NStephan Linz <linz@li-pro.net>
Signed-off-by: NMichal Simek <monstr@monstr.eu>

Signed-off-by: NStephan Linz <linz@li-pro.net>
Signed-off-by: NMichal Simek <monstr@monstr.eu>