Introduce the LMB lib used on PPC in the kernel as a clean way to manage
the memory spaces used by various boot images and structures.  This code
will allow us to simplify the code in bootm and its support functions.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>

For historical reasons we limited the stack to 256M because some boards
could only map that much via BATS.  However newer boards are capable of
mapping more memory (for example 85xx is capable of doing up to 2G).
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
Acked-by: NMarian Balakowicz <m8@semihalf.com>

Changed image_get_ramdisk() to just return NULL on error and have
get_ramdisk() propogate that error to the caller.  It's left to the
caller to call do_reset() if it wants to.

Also moved calling do_reset() in get_fdt() and fdt_relocate() on ppc
to a common location.  In the future we will change get_fdt() and
fdt_relocate() to return success/failure and not call do_reset() at all.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
Acked-by: NMarian Balakowicz <m8@semihalf.com>

Doing the fdt before the ramdisk allows us to grow the fdt w/o concern
however it does mean we have to go in and fixup the initrd info since
we don't know where it will be.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>

If we are bootin OF style than we can skip setting up some things
that are used for the old boot method.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
Acked-by: NMarian Balakowicz <m8@semihalf.com>

We don't actually need the kdb param as we are just using it to get
bd->bi_memsize which we can get from gd->bd->bi_memsize.  Also, if we
boot via OF we might not actually fill out a kdb.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
Acked-by: NMarian Balakowicz <m8@semihalf.com>

Dual format image code must properly handle all three FDT passing methods:
- raw FDT blob passed
- FDT blob embedded in the legacy uImage
- FDT blob embedded in the new uImage

This patch enables proper raw FDT handling when no FIT imaeg support
is compiled in. This is a bit tricky as we must dected FIT format even
when FIT uImage handling is not enabled as both FIT uImages and raw FDT
blobs use tha same low level format (libfdt).
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

FDT blob may be passed either: (1) raw (2) or embedded in the legacy uImage
(3) or embedded in the new uImage. For the (2) case embedding image must be
verified before we get FDT from it. This patch factors out legacy image
specific verification routine to the separate helper routine.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>
Acked-by: NKumar Gala <galak@kernel.crashing.org>

Legacy image specific verification is factored out to a separate helper
routine to keep get_kernel() generic and simple.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>
Acked-by: NKumar Gala <galak@kernel.crashing.org>

Do not pass image verification flag directly to related routines.
Simplify argument passing and move it to the bootm_header structure which
contains curently processed image specific data and is already being passed
on the argument list.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>
Acked-by: NKumar Gala <galak@kernel.crashing.org>

Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

When CONFIG_HAS_DATAFLASH is not defined gen_get_image() routine has nothing
to do, update its control flow to better reflect that simple case.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>
Acked-by: NKumar Gala <galak@kernel.crashing.org>

PPC specific FDT blob handling code is divided into two separate routines:

get_fdt()	- find and verify a FDT blob (either raw or image embedded)
fdt_relocate()	- move FDT blob to within BOOTMAP if needed
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>
Acked-by: NKumar Gala <galak@kernel.crashing.org>

This patch adds framework for dual format images. Format detection is added
and the bootm controll flow is updated to include cases for new FIT format
uImages.

When the legacy (image_header based) format is detected appropriate
legacy specific handling is invoked. For the new (FIT based) format uImages
dual boot framework has a minial support, that will only print out a
corresponding debug messages. Implementation of the FIT specific handling will
be added in following patches.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

Introducing routines for parsing new uImage format bootm arguments:
[<addr>]#<conf>		- configuration specification
[<addr>]:<subimg>	- subimage specification

New format images can contain multiple subimages of the same type. For example
a single new format image file can contain three kernels, two ramdisks and a
couple of FDT blobs. Subimage and configuration specifications are extensions
to bootm (and other image-related commands) arguments' syntax that allow to
specify which particular subimage should be operated on.

Subimage specification is used to denote a particular subimage. Configurations
are a bit more complex -- they are used to define a particualr booting setup,
for example a (kernel, fdt blob) pair, or a (kernel, ramdisk, fdt blob) tuple,
etc.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

This routine assures that image (whether legacy or FIT) is not
in a special dataflash storage.

If image address is a dataflash address image is moved to system RAM.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

New uImage format (Flattened Image Tree) requires libfdt
functionality, print out error message if CONFIG_OF_LIBFDT
is not defined.

New uImage support is enabled by defining CONFIG_FIT (and CONFIG_OF_LIBFDT).
This commit turns it on by default.
Signed-off-by: NMarian Balakowicz <m8@semihalf.com>

The CPU POST test code (run from cpu_post_exec_31()) doesn't follow the
ABI carefully, at least the CR3, CR4, and CR5 fields of CR are clobbered
by it. The gcc-4.2 with its more aggressive optimization exposes this fact.
This patch just saves the CR value before running the test code, so allowing
it to do anything it wants with CR.
Signed-off-by: NDmitry Rakhchev <rda@emcraft.com>
Acked-by: NYuri Tikhonov <yur@emcraft.com>
--

Signed-off-by: NJean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>

fix mmc_bread function prototype
Signed-off-by: NJean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>

Signed-off-by: NJean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>

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

The option CONFIG_I2C_MULTI_BUS does not have any effect on Sequoia, the
PPC440EPx reference platform, because IIC1 is never enabled. Add Sequoia board
code to turn on IIC1 if CONFIG_I2C_MULTI_BUS is selected.
Signed-off-by: NMike Nuss <mike@terascala.com>
Cc: Stefan Roese <sr@denx.de>

- hcu4.h: Removed define of CONFIG_PPC405GPr
- Corrected phy addresses
- Fix boot variables
- Respect line length of 80 chars
Signed-off-by: NNiklaus Giger <niklaus.giger@netstal.com>

- Fix some coding style violations.
- Use in/out_u16/32 where appropriate.
- Use register names from ppc405.h.
- Fix trace useage for Lauterbach.
- Remove obsolete generation HCU2.
- Renamed fixed_hcu4_sdram to init_ppc405_sdram.
Signed-off-by: NNiklaus Giger <niklaus.giger@netstal.com>

Signed-off-by: NNiklaus Giger <niklaus.giger@netstal.com>

Signed-off-by: NLarry Johnson <lrj@acm.org>

This patch tries to get rid of some assembler warnings about
changed .got2 section type while compiling x86 bios emulator
code.
Signed-off-by: NAnatolij Gustschin <agust@denx.de>

Signed-off-by: NAnatolij Gustschin <agust@denx.de>