u-boot.git/lib_m68k, branch v1.3.3

Fix implicit declaration build warnings

2008-05-03T21:30:21+00:00

- warning: implicit declaration of function ‘serial_initialize’

Signed-off-by: Marcel Ziswiler

Restore the ability to continue booting after legacy image overwrite

2008-04-18T06:59:05+00:00

Before new uImage code was merged, bootm code allowed for the kernel image to
get overwritten during decompresion. new uImage introduced a check for image
overwrites and refused to boot the image that got overwritten. This patch
restores the old behavior. It also adds a warning when the image overwriten is
a multi-image file, because in such case accessing componentes other than the
first one will fail.

Signed-off-by: Marian Balakowicz

[new uImage] Add new uImage format support to arch specific do_bootm_linux() routines

2008-03-12T09:33:00+00:00

This patch updates architecture specific implementations of
do_bootm_linux() adding new uImage format handling for
operations like get kernel entry point address, get kernel
image data start address.

Signed-off-by: Marian Balakowicz

[new uImage] Remove unnecessary arguments passed to ramdisk routines

2008-03-12T09:14:38+00:00

boot_get_ramdisk() and image_get_ramdisk() do not need all
cmdtp, flag, argc and argv arguments. Simplify routines definition.

Signed-off-by: Marian Balakowicz

[new uImage] Update naming convention for bootm/uImage related code

2008-02-29T13:58:34+00:00

This patch introduces the following prefix convention for the
image format handling and bootm related code:

genimg_		- dual format shared code
image_		- legacy uImage format specific code
fit_		- new uImage format specific code
boot_		- booting process related code

Related routines are renamed and a few pieces of code are moved around and
re-grouped.

Signed-off-by: Marian Balakowicz

[new uImage] Respect autostart setting in linux bootm

2008-02-29T12:15:56+00:00

Signed-off-by: Kumar Gala 
Acked-by: Marian Balakowicz

[new uImage] Provide ability to restrict region used for boot images

2008-02-29T12:15:56+00:00

Allow the user to set 'bootm_low' and 'bootm_size' env vars as a way
to restrict what memory range is used for bootm.

Signed-off-by: Kumar Gala 
Acked-by: Marian Balakowicz

[new uImage] Use lmb for bootm allocations

2008-02-29T12:15:56+00:00

Convert generic ramdisk_high(), get_boot_cmdline(), get_boot_kbd()
functions over to using lmb for allocation of the ramdisk, command line
and kernel bd info.

Convert PPC specific fdt_relocate() to use lmb for allocation of the device
tree.

Provided a weak function that board code can call to do additional
lmb reserves if needed.

Also introduce the concept of bootmap_base to specify the offset in
physical memory that the bootmap is located at.  This is used for
allocations of the cmdline, kernel bd, and device tree as they should
be contained within bootmap_base and bootmap_base + CFG_BOOTMAPSZ.

Signed-off-by: Kumar Gala

[new uImage] rework error handling so common functions don't reset

2008-02-29T11:32:50+00:00

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: Kumar Gala 
Acked-by: Marian Balakowicz

[new uImage] Don't pass kdb to ramdisk_high since we may not have one

2008-02-29T11:27:21+00:00

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: Kumar Gala 
Acked-by: Marian Balakowicz