Now that the linker script is preprocessed with -ansi, there is no need to
manually undef the bfin define.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

Signed-off-by: NMike Frysinger <vapier@gentoo.org>

If someone uses the FDPIC toolchain to compile U-Boot, make sure the
linker knows to use the normal ABI target rather than the FDPIC one.
This wasn't needed with older toolchains, but when we fixed the linker
such that the default target changed based on tuple, this broke.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

Scrub a lot of dead cruft in the process.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

Switch to the SMC911X driver by default now, and fix LDR env settings.
Signed-off-by: NHarald Krapfenbauer <Harald.Krapfenbauer@bluetechnix.at>
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

We tweak the configs a little when doing automated hardware tests.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

The strictest alignment on Blackfin systems is 32bits (since that is the
largest load instruction), so don't force 256byte alignment here.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

The reloc_off member no longer exists, so drop it.  Also change this
function so that it is always compiled and prevents latent issues like
this in the future.
Reported-by: NPeter Meerwald <pmeerw@pmeerw.net>
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

There is no Blackfin/NetBSD port, so enabling support for it by default
doesn't make any sense.
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

Signed-off-by: NWolfgang Denk <wd@denx.de>

As this seems unclear, document how the flow of setting up
the MAC address is correct.
Signed-off-by: NHeiko Schocher <hs@denx.de>

Text changed slightly, adding input from Mike Frysinger.
Signed-off-by: NWolfgang Denk <wd@denx.de>

Only fill the device enetaddr with the contents of the eeprom,
do not program it in MAC address registers
Signed-off-by: NHeiko Schocher <hs@denx.de>
Acked-by: NBen Warren <biggerbadderben@gmail.com>

The ramdisk sections in doc/uImage.FIT/multi.its lack
load address and entry point properties. Using examples
from this file will result in unbootable image, u-boot
will issue the following error messages:

Can't get ramdisk subimage load address!
Ramdisk image is corrupt or invalid

This patch adds missing properties to ramdisk sections.
Signed-off-by: NFelix Radensky <felix@embedded-sol.com>

$ ./MAKEALL suen3
jffs2_1pass.c: In function 'get_fl_mem':
jffs2_1pass.c:399: warning: unused variable 'id'
jffs2_1pass.c: In function 'get_node_mem':
jffs2_1pass.c:423: warning: unused variable 'id'
Signed-off-by: NHeiko Schocher <hs@denx.de>
Tested-by: NTom <Tom.Rix@windriver.com>

After determining how much DDR is actually in the system, set DBAT0 and
IBAT0 accordingly.  This ensures that the CPU won't attempt to access
(via speculation) addresses outside of actual memory.

On 86xx systems, DBAT0 and IBAT0 (the BATs for DDR) are initialized to 2GB
and kept that way.  If the system has less than 2GB of memory (typical for
an MPC8610 HPCD), the CPU may attempt to access this memory during
speculation.  The zlib code is notorious for generating such memory reads,
and indeed on the MPC8610, uncompressing the Linux kernel causes a machine
check (without this patch).

Currently we are limited to power of two sized DDR since we only use a
single bat.  If a non-power of two size is used that is less than
CONFIG_MAX_MEM_MAPPED u-boot will crash.
Signed-off-by: NTimur Tabi <timur@freescale.com>
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>

Use the same code between primary and secondary cores to init the
L1 cache.  We were not enabling cache parity on the secondary cores.

Also, reworked the L1 cache init code to match the e500mc L2 init code
that first invalidates the cache and locks.  Than enables the cache and
makes sure its enabled before continuing.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>

This patch fixes a problem introduced with patch eb5eb2b0
[ppc4xx: Cleanup PPC4xx I2C infrastructure]. We need to assign the I2C
base address to the "i2c" pointer inside of the controller loop.
Otherwise controller 0 is initialized multiple times instead of
initializing each I2C controller sequentially.

Tested on Katmai.
Signed-off-by: NStefan Roese <sr@denx.de>
Acked-by: NHeiko Schocher <hs@denx.de>

Booting a "Multi-File Image" including a linux kernel, ramdisk and
fdt, generated with

mkimage -A ppc \
    -O linux \
    -T multi \
    -C gzip \
    -a 00000000 \
    -e 00000000 \
    -n "kernel-2.6+initrd+dtb" \
    -d "vmlinux.bin.gz:ramdisk_image.gz:board.dtb" \
    multi.bin

actually fails, because ramdisk start and end addresses
didn;t get initialized. This patch fixes this issue.

Tested on the KUP4K board.
Signed-off-by: NHeiko Schocher <hs@denx.de>

and removed it from the .h file
Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>

The code to parse alen appeared 6 times in the function.
Factored this out in a small helper function
Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>

Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>

Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>

Declared all functions that were not called outside the file as static
Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>

Update CHANGELOG
Signed-off-by: NWolfgang Denk <wd@denx.de>

Signed-off-by: NWolfgang Denk <wd@denx.de>

The ml300 board has a number of issues, but nobody cares about this
long-orphaned board any more.  Remove it.
Signed-off-by: NWolfgang Denk <wd@denx.de>
Acked-by: NMichal Simek <monstr@monstr.eu>

The restructuring of the mkimage command in commit 89a4d6b1 ("tools:
mkimage: split code into core, default and FIT image specific")
introduced a bug that caused mkimage to segfault when run without
"-n name" option.  Initialize the imagename entry to prevent that.
Signed-off-by: NWolfgang Denk <wd@denx.de>

This patch adds status polling method to offer an alternative to
data toggle method for amd flash chips.

This patch is needed for nios2 cfi flash interface, where the bus
controller performs 4 bytes read cycles for a single byte read
instruction. The data toggle method can not detect chip busy
status correctly. So we have to poll DQ7, which will be inverted
when the chip is busy.

This feature is enabled with the config def,
CONFIG_SYS_CFI_FLASH_STATUS_POLL
Signed-off-by: NThomas Chou <thomas@wytron.com.tw>
Signed-off-by: NStefan Roese <sr@denx.de>

With old configuration it could happen tout=0 if CONFIG_SYS_HZ<1000.
Signed-off-by: NRenato Andreola <renato.andreola@imagos.it>
Signed-off-by: NAlessandro Rubini <rubini@gnudd.com>
Signed-off-by: NThomas Chou <thomas@wytron.com.tw>
Signed-off-by: NStefan Roese <sr@denx.de>

The ATMEL flash does not have buffer write feature. Assgined
buffer_size = 1, so that when there is a write to the flash
will not use buffer write function.
Signed-off-by: NTsiChung Liew <tsicliew@gmail.com>

The flash location is at 0xff800000, not 0
Signed-off-by: NTsiChung Liew <tsicliew@gmail.com>

The CF will call cache functions in lib_m68/cache.c and the
cache settings are defined in platform configuration file.
Signed-off-by: NTsiChung Liew <tsicliew@gmail.com>