u-boot.git/common, branch v1.3.4

85xx: Rename CONFIG_NR_CPUS to CONFIG_NUM_CPUS

2008-08-11T22:09:29+00:00

Use CONFIG_NUM_CPUS to match existing define used by 86xx.

Signed-off-by: Kumar Gala 
Acked-by: Jon Loeliger

Fix fallout from autostart revert

2008-08-11T22:06:34+00:00

The autostart revert caused a bit of duplicated code as well as
code that was using images->autostart that needs to get removed so
we can build again.

Signed-off-by: Kumar Gala

common/cmd_load.c - Minor code & Coding Style cleanup

2008-08-10T22:13:27+00:00

- os_data_header Variable is a carry over feature
   & unused. So removed all instance of this variable
 - Minor Code Style Update

Signed-off-by: Gururaja Hebbar 
Acked-by: Jean-Christophe PLAGNIOL-VILLARD

OneNAND: Remove base address offset usage

2008-08-10T20:45:04+00:00

While locally preparing some U-Boot patches for ARM based OMAP3 boards, some
using OneNAND and some using NAND, we found some differences in OneNAND and
NAND command address handling.

As this might confuse users (it already confused us), we like to align OneNAND
and NAND address handling.

The issue is that cmd_onenand.c subtracts the onenand base address from the
addresses you type into the u-boot command line so, unlike nand, you can't
use addresses relative to the start of the onenand part e.g. this won't work:

onenand read 82000000 280000 400000

you have to use:

onenand read 82000000 20280000 400000

Looking at recent git, the only board currently using OneNAND is Apollon, and
for this the OneNAND base address is 0 (apollon.h)

#define	CFG_ONENAND_BASE	0x00000000

so patch below won't break any existing boards and will align OneNAND and NAND
handling on boards where OneNAND base address is != 0.

Signed-off-by: Steve Sakoman 
Signed-off-by: Manikandan Pillai 
Signed-off-by: Dirk Behme

Revert "[new uImage] Add autostart flag to bootm_headers structure"

2008-08-09T23:26:26+00:00

This reverts commit f5614e7926863bf0225ec860d9b319741a9c4004.

The commit was based on a misunderstanding of the (documented)
meaning of the 'autostart' environment variable. It might cause
boards to hang if 'autostart' was used, with the potential to brick
them. Go back to the documented behaviour.

Conflicts:

	common/cmd_bootm.c
	common/image.c
	include/image.h

Signed-off-by: Wolfgang Denk

FIT: Fix handling of images without ramdisks

2008-08-09T15:36:06+00:00

boot_get_ramdisk() should not treat the case when a FIT image does
not contain a ramdisk as an error.

Signed-off-by: Peter Tyser 
Acked-by: Michal Simek

TQM823L: re-enable logo support; update LCD_INFO text

2008-08-08T14:43:01+00:00

Signed-off-by: Wolfgang Denk

Fix bitmap display for atmel lcd controller

2008-08-01T10:42:50+00:00

The current lcd_display_bitmap() function does not work properly
for the Atmel LCD controller.

2 fixes need to be done:-

(a) when setting the colour map, use the lcd_setcolreg() function
    as provided by the Atmel driver
(b) the data is never actually written to the lcd framebuffer !!

Signed-off-by: Mark Jackson

Merge branch 'master' of ssh://10.10.0.7/home/wd/git/u-boot/master

2008-07-31T15:50:37+00:00

Add gzipped logo support

2008-07-31T15:48:50+00:00

The README file states that CONFIG_VIDEO_BMP_GZIP behaves as follows:

  If this option is set, additionally to standard BMP
  images, gzipped BMP images can be displayed via the
  splashscreen support or the bmp command.

However, the splashscreen function *only* supports standard BMP images.

This patch adds the documented gzip support.

Signed-off-by: Mark Jackson