This allows for arbitrarily long manufacturer ids following the JEDEC
standard of 0x7f continuation bytes.  It also makes adding new entries
easier as it's just one element in an array.  The downside is that it
increases code size a bit, but we're talking ~50 bytes.
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

This patch does 2 things:
 - Fix the argument number assigned to the vdw (VME data width) value.
   Previously, a nonexistent 7th arument was read as the vdw variable.

 - Reduce the size of the argument array for the tsi148 command from
   8 to 7.  The tsi148 command itself is argument index 0, and the
   maximum number arguments passed to the command is 6, making a total
   of 7 for the array.
Signed-off-by: NBrent Darley <bdarley@xes-inc.com>
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

No boards utilize the warm reset entry point, so remove it.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

Previously the _warm_start label was used as an entry point.  These 2
entry points should be functionally identical after the removal of the
BOOTFLAG_WARM define.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

This puts the board info struct in a known state and allows the removal
of other code which initialized board info fields to 0.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

On some boards with a very short watchdog timeout, the "cp" and
"cmp" commands may reset the board. This patch adds some
watchdog resets inside the loops. Otherwise for example the lwmon5
board will reset while doing something like this:

=> cp.b fc000000 1000000 100000
Signed-off-by: NStefan Roese <sr@denx.de>

Using -fno-toplevel-reorder causes gcc to not reorder functions.  This
ensures that an application's entry point will be the first function in
the application's source file.

This change, along with commit 620bbba5
should cause a standalone application's entry point to be at the base of
the compiled binary.  Previously, the entry point could change depending
on gcc version and flags.

Note -fno-toplevel-reorder is only available in gcc version 4.2 or
greater.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.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>

The U-Boot code has the following bugs related to the processing of Long File
Name (LFN) entries scattered across several clusters/sectors :

1) get_vfatname() function is designed to gather scattered LFN entries by
cluster chain processing - that doesn't work for FAT12/16 root directory.
In other words, the function expects the following input data:
 1.1) FAT32 directory (which is cluster chain based);
        OR
 1.2) FAT12/16 non-root directory (which is also cluster chain based);
        OR
 1.3) FAT12/16 root directory (allocated as contiguous sectors area), but
 all necessary information MUST be within the input buffer of filesystem cluster
 size (thus cluster-chain jump is never initiated).

In order to accomplish the last condition, root directory parsing code in
do_fat_read() uses the following trick: read-out cluster-size block, process
only first sector (512 bytes), then shift 512 forward, read-out cluster-size
block and so on. This works great unless cluster size is equal to 512 bytes
(in a case you have a small partition), or long file name entries are scattered
across three sectors, see 4) for details.

2) Despite of the fact that get_vfatname() supports FAT32 root directory
browsing, do_fat_read() function doesn't send current cluster number correctly,
so root directory look-up doesn't work correctly.

3) get_vfatname() doesn't gather scattered entries correctly also is the case
when all LFN entries are located at the end of the source cluster, but real
directory entry (which must be returned) is at the only beginning of the
next one. No error detected, the resulting directory entry returned contains
a semi-random information (wrong size, wrong start cluster number and so on)
i.e. the entry is not accessible.

4) LFN (VFAT) allows up to 20 entries (slots) each containing 26 bytes (13
UTF-16 code units) to represent a single long file name i.e. up to 520 bytes.
U-Boot allocates 256 bytes buffer instead, i.e. 10 or more LFN slots record
may cause buffer overflow / memory corruption.
Also, it's worth to mention that 20+1 slots occupy 672 bytes space which may
take more than one cluster of 512 bytes (medium-size FAT32 or small FAT16
partition) - get_vfatname() function doesn't support such case as well.

The patch attached fixes these problems in the following way:
- keep using 256 bytes buffer for a long file name, but safely prevent a
possible buffer overflow (skip LFN processing, if it contains 10 or more
slots).

- explicitly specify FAT12/16 root directory parsing buffer size, instead
of relying on cluster size. The value used is a double sector size (to store
current sector and the next one). This fixes the first problem and increases
performance on big FAT12/16 partitions;

- send current cluster number (FAT32) to get_vfatname() during root
directory processing;

- use LFN counter to seek the real directory entry in get_vfatname() - fixes the
third problem;

- skip deleted entries in the root directory (to prevent bogus buffer
overflow detection and LFN counter steps).

Note: it's not advised to split up the patch, because a separate part may
operate incorrectly.
Signed-off-by: NMikhail Zolotaryov <lebon@lebon.org.ua>

Commit d984fed0 (makefiles: fixes for building build tools)
changed the variable name FIT_CFLAGS to HOSTCFLAGS_NOPED
but forgot to update to corresponding comment.
Signed-off-by: NDaniel Hobi <daniel.hobi@schmid-telecom.ch>
Cc: Scott Wood <scottwood@freescale.com>
Cc: Wolfgang Denk <wd@denx.de>

When use the CONFIG_ENV_IS_NOWHERE, I met such issue:

	DRAM:  256 MiB
	Using default environment

	*** Warning - bad CRC, using default environment
Signed-off-by: NLei Wen <leiwen@marvell.com>

Patch 253cb831 [zlib: add watchdog reset call] added already a few
watchdog reset calls to the new zlib U-Boot port. But on some boards
this is not enough. Additional calls are needed on boards with
short watchdog timeouts.

This was detected and tested on the lwmon5 board with a very short
watchdog timeout. Without this patch, the board resets during Linux
kernel decompression. With it, the decompression succeeds.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Detlev Zundel <dzu@denx.de>
Acked-by: NDetlev Zundel <dzu@denx.de>

As usually done in U-Boot, the watchdog_reset code is called via a
macro (WATCHDOG_RESET). In zlib.c this was done differently, by using
a function pointer which is initialized with WATCHDOG_RESET upon watchdog
usage or with NULL otherwise. This patch now uses the plain
WATCHDOG_RESET macros to call the function resulting in slightly smaller
U-Boot images and simpler code.

U-Boot code size reduction:

PowerPC board with watchdog support (lwmon5):
-> 80 bytes smaller image size

PowerPC board without watchdog support (sequoia):
-> 112 bytes smaller image size
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Detlev Zundel <dzu@denx.de>
Cc: Wolfgang Denk <wd@denx.de>
Acked-by: NDetlev Zundel <dzu@denx.de>

PDM360NG board uses this functionality to pass display
timing info to the Linux Framebuffer driver.
Signed-off-by: NAnatolij Gustschin <agust@denx.de>
Acked-by: NDetlev Zundel <dzu@denx.de>

Boards can pass display timing info for drivers using EDID
block. Provide common function to add board specific EDID
data to the device tree. Subsequent patch makes use of this
functionality.

Detailed timing descriptor data from EDID is used for
programming the display controller. This is currently
implemented on the Linux side by the fsl-diu-fb frame
buffer driver and it is documented there in
Documentation/powerpc/dts-bindings/fsl/diu.txt.
Signed-off-by: NAnatolij Gustschin <agust@denx.de>
Acked-by: NDetlev Zundel <dzu@denx.de>
Cc: Gerald Van Baren <vanbaren@cideas.com>

The include <jffs2/jffs2.h> is still necessary though.
Signed-off-by: NAlexander Stein <alexander.stein@systec-electronic.com>
Acked-by: NStefan Roese <sr@denx.de>

When a CFI flash chip could not be detected an error message similar to
the following would be printed on bootup:

 FLASH: ## Unknown FLASH on Bank 1 - Size = 0x01000000 = 0 MB

The printf incorrectly converted the flash size into megabytes.  This
patch fixes the printing of the flash size in megabytes:

 FLASH: ## Unknown FLASH on Bank 1 - Size = 0x01000000 = 16 MB
Signed-off-by: NJohn Schmoller <jschmoller@xes-inc.com>
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>
Signed-off-by: NStefan Roese <sr@denx.de>

Microblaze little-endian toolchain should export
__MICROBLAZEEL__.
Signed-off-by: NMichal Simek <monstr@monstr.eu>

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>

Add smc_write_hwaddr() to set mac address.
Clear dev before use.
Signed-off-by: NThomas Chou <thomas@wytron.com.tw>
Acked-by: NMike Frysinger <vapier@gentoo.org>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

This patch proposes to migrate the davinci_emac driver to using the
eth_device->write_hwaddr function pointer as suggested by Ben Warren.

All the davinci boards had the behaviour, prior to this patch, of
sync'ing the environment variable enetaddr with the MAC address read
from non-volatile storage on boot -- when the two locations disagreed,
the environment variable value took precendence. This patch keeps the
same behaviour but lets eth_initialize take care of it.

This patch refactors davinci_emac setup in the boards so that the MAC
address is read from non-volatile storage into the environment variable
and then the environment variable value is use in eth_intialize. The
only exception is the direct call to davinci_eth_set_mac_addr made by
the da830evm board init which was changed into an assignment of the
enetaddr field.
Signed-off-by: NBen Gardiner <bengardiner@nanometrics.ca>
Tested-by: NNick Thompson <nick.thompson@ge.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Emaclite was using old net api that's why
this patch move emaclite to NET_MULTI api.
Signed-off-by: NMichal Simek <monstr@monstr.eu>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Most people don't use the 'rarpboot' command, so only enable it when
CONFIG_CMD_RARP is defined.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Support New emaclite AXI IP.
Signed-off-by: NMichal Simek <monstr@monstr.eu>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Some boards need their board-specific PHY quirks to be called
to PHY to work normally. As mpc5xxx_fec driver uses on demand
PHY initialization and can even reinit PHY during normal operation
we can't count on reset_phy() call from arch/<arch>/lib/board.c
(it is most likely called _before_ we init the PHY from the
driver) so we need to add call to reset_phy() directly in the
driver.
Signed-off-by: NIlya Yanok <yanok@emcraft.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Some return values pretended correct pass. This patch changes them according
to README.drivers.net. This patch changes e.g. command 'dhcp' to stop after
errorneous autonegotiation.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

This patch increases timeout for autonegotiation from 1 second to 3 seconds.
Some boards (e.g. at91rm9200ek) did not negotiate within 1 second.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

V3: further refinements:
- use priv member instead of container method
- allow setting of MAC address by write_hwaddr method
- avoid shutting down link between commands
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

Instead of always performing an autoneg, check if the PHY
already has a link and if it matches one of the requested
modes. Initially only 100MbFD is optimized this way.
Signed-off-by: NJoakim Tjernlund <Joakim.Tjernlund@transmode.se>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

All are within an #ifdef CONFIG_NET_MULTI block already
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>

This udelay looks bogus and doesn't help my board.
Signed-off-by: NJoakim Tjernlund <Joakim.Tjernlund@transmode.se>
Acked-by: NKim Phillips <kim.phillips@freescale.com>
Signed-off-by: NBen Warren <biggerbadderben@gmail.com>