This patch adds support for the Palm Tungsten|C PXA255 board. The support
includes:
- LCD
- MMC
- UART
- NOR
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

This LCD panel is found in Palm LifeDrive handheld
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

ACX517AKN LCD panel is found in Palm Tungsten|C
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

Also change the initializer style
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

Conflicts:
	arch/arm/include/asm/config.h
	board/LaCie/edminiv2/config.mk
	board/karo/tx25/config.mk
	board/logicpd/imx27lite/config.mk
	doc/README.arm-relocation
Signed-off-by: NWolfgang Denk <wd@denx.de>

Conflicts:
	board/logicpd/imx31_litekit/config.mk
	boards.cfg
Signed-off-by: NWolfgang Denk <wd@denx.de>

clock.c / timer.c used static data and are called before relocation.
Move all static variables into global_data structure. Also cleanup
timer.c from unused stubs and make it truly use 64 bit tick values.
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>

This patch enables USB for at91rm9200ek board.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>

This patch fixes arch-at91/hardware.h to have the relevant defines for
at91rm9200 devices to support existing at91 usb driver.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>

This patch removes some functionality from at91rm9200ek board but the
remaining functionality does now work with newer at91 code and
arm-relocation.

Currently missing features are:
 - dataflash booting (due to missing HW for testing)
 - MMC/SD-Card
 - first stage bootloader support is completely removed (not needed for
   NOR)

Cause this board was (some days ago) reference for all at91rm9200 based
boards this should be a good starting point to convert all remaining
at91rm9200 borads to at91 code. Aside from that this is a good base to
get some drivers between at91sam/at91rm/avr32 merged.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
Signed-off-by: NReinhard Meyer <u-boot@emk-elektronik.de>

Fix flash memory map and other updates for QONG board:

- adjust/fix "kernel_addr" settings
- adjust/fix mtdparts NOR flash settings
- add mtdparts NAND flash mapping
- sort command list
- enable "setexpr" command
- enable ext2 support
- delete bogus comment
Signed-off-by: NWolfgang Denk <wd@denx.de>
Cc: Stefano Babic <sbabic@denx.de>

Tested on hardware. Boots Linux nicely.
Signed-off-by: NMagnus Lilja <lilja.magnus@gmail.com>

This code section is dead due to we never define
ENABLE_IMPRECISE_ABORT for MX5
Signed-off-by: NJason Liu <r64343@freescale.com>

For testing ARM device tree support
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>
Acked-by: NWolfgang Denk <wd@denx.de>

Based on other architectures already supported.
Tested on OMAP3 Beagle board and another unnamed ARM platform.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>
Tested-by: NRob Herring <rob.herring@smooth-stone.com>
Acked-by: NWolfgang Denk <wd@denx.de>

The routines boot_ramdisk_high, boot_get_cmdline and boot_get_kbd
are currently enabled by various combinations of CONFIG_M68K,
CONFIG_POWERPC and CONFIG_SPARC.

Use CONFIG_SYS_BOOT_<FEATURE> defines instead.

CONFIG_SYS_BOOT_RAMDISK_HIGH
CONFIG_SYS_BOOT_GET_CMDLINE
CONFIG_SYS_BOOT_GET_KBD

Define these as appropriate in arch/include/asm/config.h files.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>
Acked-by: NWolfgang Denk <wd@denx.de>

All arches except nios2 and microblaze call boot_get_fdt
from bootm_start in common/cmd_bootm.c.

Having nios2 and microblaze do so as well removes code from
their respective do_bootm_linux routines and allows removal of
a nasty ifdef from bootm_start.

In the case where boot_get_fdt returns an error bootm_start
returns and the platform specific do_bootm_linux routines
will never get called.

Also only check argv[3] for an fdt addr if argc > 3 first.
This is already the case for nios2.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>
CC: Scott McNutt <smcnutt@psyent.com>
CC: Michal Simek <monstr@monstr.eu>
CC: Thomas Chou <thomas@wytron.com.tw>
Acked-by: NWolfgang Denk <wd@denx.de>
Acked-by: NMichal Simek <monstr@monstr.eu>
Tested-by: NThomas Chou <thomas@wytron.com.tw>

Add fdt_fixup_memory_banks and reimplement fdt_fixup_memory
using it.  Tested on OMAP3 beagle board with two banks of
memory.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>
CC: Jerry Van Baren <vanbaren@cideas.com>
Acked-by: NGerald Van Baren <vanbaren@cideas.com>

fdt_totalsize returns size in cpu endian so don't call be32_to_cpu
on the result.  This was harmless on big endian platforms but not
on little endian ARMs.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>

boot_relocate_fdt is called on platforms with CONFIG_SYS_BOOTMAPSZ
defined to relocate the device tree blob to be inside the
boot map area between bootmap_base and bootmap_base+CONFIG_SYS_BOOTMAPSZ.

For the case where the blob needs to be relocated, space is
allocated inside the bootmap by calling lmb_alloc_base with
size passed in plus some padding:

    of_len = *of_size + CONFIG_SYS_FDT_PAD;

For the case where the blob is already inside the bounds of the boot map
area, lmb_reserve is called to reserve the the space where the blob is
already residing.  The calculation for this case is currently:

    of_len = (CONFIG_SYS_BOOTMAPSZ + bootmap_base) - (ulong)fdt_blob;

This is wrong because it reserves all the space in the boot map area
from the blob to the end ignoring completely the actual size. The
worst case is where the blob is at the beginning and the entire boot map
area get reserved. Fix this by changing the length calculation to this:

    of_len = *of_size + CONFIG_SYS_FDT_PAD;

This bug has likely never manifested itself because bootm has never
been called with the fdt blob already in the bootmap area.  In my
testing on an OMAP3 beagle board I initially worked around the bug
by simply moving the initial location of the fdt blob.  I have tested
with the new calculation with the fdt blob both inside and outside
the boot map area.
Signed-off-by: NJohn Rigby <john.rigby@linaro.org>

Fix these warnings:
dlmalloc.c: In function 'free':
dlmalloc.c:2507: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules
dlmalloc.c:2507: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules
dlmalloc.c:2507: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules

Some page(http://blog.worldofcoding.com/2010/02/solving-gcc-44-strict-aliasing-problems.html)
suggests adding __attribute__((__may_alias__)). Doing so makes the warnings go away.
Signed-off-by: NJoakim Tjernlund <Joakim.Tjernlund@transmode.se>
Acked-by: NMike Frysinger <vapier@gentoo.org>

The fixup routine must not fixup NULL pointers.
Problem can be seen by
 char *testfun(void) __attribute__((weak));
 char *(*myfun)(void) = testfun;

Then add
  printf("myfun:%p, &myfun:%p\n", myfun, &myfun);
before relocation and after relocation.
myfun should be NULL in both cases but it is not.
Signed-off-by: NJoakim Tjernlund <Joakim.Tjernlund@transmode.se>

Now that warm booting is not supported, there isn't a need for the
BOOTFLAG_COLD and BOOTFLAG_WARM defines, so remove them.

Note that this change makes the board info bd_bootflags field useless.
It will always be set to 0, but we leave it around so that we don't
break the board info structure that some OSes are expecting to be passed
from U-Boot.
Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>

Signed-off-by: NFrancesco Rendine <francesco.rendine@valueteam.com>
Signed-off-by: NDamien Dusha <d.dusha@gmail.com>
Signed-off-by: NAnatolij Gustschin <agust@denx.de>

Coding style cleanup; slight file restructuring.
Signed-off-by: NWolfgang Denk <wd@denx.de>
Acked-by: NRemy Bohmer <linux@bohmer.net>

I'm noticed that IGEP maintainer isn't in the correct place within
the ARM subsection: it's supposed to be in alphabetical order by
maintainer. This patch fix this.
Signed-off-by: NEnric Balletbo i Serra <eballetbo@iseebcn.com>

After the recent cleanups, a number of config.mk files consist only of
a "PLATFORM_CPPFLAGS += -I$(TOPDIR)/board" entry whih is not needed.
Remove such entries.  In most cases, that means that the whole
config.mk file can be removed.
Signed-off-by: NWolfgang Denk <wd@denx.de>

Add command line handling to select boards to be built by
architecture, CPU family, vendor or SoC name.
Signed-off-by: NWolfgang Denk <wd@denx.de>

Clean up Makefile, and drop a lot of the config.mk files on the way.

We now also automatically pick all boards that are listed in
boards.cfg (and with all configurations), so we can drop the redundant
entries from MAKEALL to avoid building these twice.
Signed-off-by: NWolfgang Denk <wd@denx.de>

When generating include/autoconfig.mk, hex numbers would be quoted.
This caused some false positives during automatic testing of the
builds, and is known to cause some real issues for some Blackfin
configurations. Don't use apostophes for decimal and hex numbers (nor
for octal numbers).
Signed-off-by: NWolfgang Denk <wd@denx.de>
Signed-off-by: NMike Frysinger <vapier@gentoo.org>

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>

There are some boards where it's currently not possible to detect all
board information at runtime, therefore a new column was added to
boards.cfg .

This column can contain multiple options: a board configuration name,
optionally followed by a colon (':') and a list of options, which are
separated by comma (',').

In case of simple options like '256M_U_BOOT', these expand to
"#define CONFIG_MK_256M_U_BOOT 1" in config.h . In case of
assignments like 'RAM=8192', these expand to "#define CONFIG_MK_RAM
8192" in config.h .

Example:

	FOO:HAS_BAR,BAZ=64

means:
	- the name of the board config file is include/configs/FOO.h
	- the generated file include/config.h will contain these
	  lines:

		#define CONFIG_HAS_BAR  1
		#define CONFIG_BAZ  64
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>

[wd@denx.de: edited commit message; added code to deal with an
optional board configuration name]
Signed-off-by: NWolfgang Denk <wd@denx.de>

"make clean" after builds of MatrixVision boards would leave stale
files around:

	board/matrix_vision/mvblm7/bootscript.img
	board/matrix_vision/mvsmr/bootscript.img

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

Commit ea533c26 changed
arg_off_size to take a pointer to a device index, rather than
to the device itself.  When updating callers, the nand unlock
code was missed.
Signed-off-by: NScott Wood <scottwood@freescale.com>