u-boot.git/include/asm-blackfin, branch v1.3.4 Unnamed repository; edit this file 'description' to name the repository. Change bd/gd memsize/ram_size to be phys_size_t. 2008-06-11T22:54:53+00:00 Becky Bruce becky.bruce@freescale.com 2008-06-10T01:37:16+00:00 b57ca3e128cc10a133ba79bc7ec3e7b50e7c8fbe Currently, both are defined as an unsigned long, but should be phys_size_t. This should result in no real change, since phys_size_t is currently an unsigned long for all the default configs. Also add print_lnum to cmd_bdinfo to deal with the potentially wider memsize. Signed-off-by: Becky Bruce <becky.bruce@freescale.com> 
Currently, both are defined as an unsigned long, but
should be phys_size_t. This should result in no real change,
since phys_size_t is currently an unsigned long for all the
default configs.  Also add print_lnum to cmd_bdinfo to deal
with the potentially wider memsize.

Signed-off-by: Becky Bruce <becky.bruce@freescale.com>
Merge branch 'lwmon5' of /home/wd/git/u-boot/projects 2008-05-20T23:13:39+00:00 Wolfgang Denk wd@denx.de 2008-05-20T23:13:39+00:00 eddc7c46c6030d6eca29ac254c9db98198be572d 






Big white-space cleanup.
2008-05-20T22:14:08+00:00

Wolfgang Denk
wd@denx.de

2008-05-20T14:00:29+00:00

53677ef18e25c97ac613349087c5cb33ae5a2741

This commit gets rid of a huge amount of silly white-space issues.
Especially, all sequences of SPACEs followed by TAB characters get
removed (unless they appear in print statements).

Also remove all embedded "vim:" and "vi:" statements which hide
indentation problems.

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





This commit gets rid of a huge amount of silly white-space issues.
Especially, all sequences of SPACEs followed by TAB characters get
removed (unless they appear in print statements).

Also remove all embedded "vim:" and "vi:" statements which hide
indentation problems.

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







POST: replace the LOGBUFF_INITIALIZED flag in gd->post_log_word (1 << 31) with the GD_FLG_LOGINIT flag in gd->flags.
2008-05-20T21:24:38+00:00

Yuri Tikhonov
yur@emcraft.com

2008-05-08T13:46:42+00:00

0e15ddd11f1a84c465e434eb051d2ef08ef02b9b

This way we become able to utilize the full post_log_word for POST
activities (overwise, POST ECC, which has 0x8000 ID, could be
erroneously treated as started in post_output_backlog() even if there
was actually no POST ECC run (because of OCM POST failure, for
example).

Signed-off-by: Yuri Tikhonov <yur@emcraft.com>





This way we become able to utilize the full post_log_word for POST
activities (overwise, POST ECC, which has 0x8000 ID, could be
erroneously treated as started in post_output_backlog() even if there
was actually no POST ECC run (because of OCM POST failure, for
example).

Signed-off-by: Yuri Tikhonov <yur@emcraft.com>







POST: add POST_STOP flag
2008-05-20T21:24:37+00:00

Yuri Tikhonov
yur@emcraft.com

2008-05-08T13:45:26+00:00

28a385065882d6cb6ac5f443311ff87887ed7c13

Don't run futher tests in case of a test fails that is marked as
POST_STOP.

Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>





Don't run futher tests in case of a test fails that is marked as
POST_STOP.

Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>







Introduce phys_size_t and move phys_addr_t into asm/types.h
2008-04-14T00:13:46+00:00

Kumar Gala
galak@kernel.crashing.org

2008-03-27T16:46:38+00:00

e99ccb488181d012248c6be30b2093e950319fc5

Also add CONFIG_PHYS_64BIT on powerpc to deal with 32-bit ppc's
that have larger physical addresses like 44x, 85xx, and 86xx.

Signed-off-by: Kumar Gala <galak@kernel.crashing.org>





Also add CONFIG_PHYS_64BIT on powerpc to deal with 32-bit ppc's
that have larger physical addresses like 44x, 85xx, and 86xx.

Signed-off-by: Kumar Gala <galak@kernel.crashing.org>







Blackfin: unify cpu and boot modes
2008-03-30T19:50:19+00:00

Mike Frysinger
vapier@gentoo.org

2008-03-30T19:46:13+00:00

9171fc81722c20fdb5a829a58b17c9eaadd5fb44

All of the duplicated code for Blackfin processors and boot modes have been
unified.  After all, the core is the same for all processors, just the
peripheral set differs (which gets handled in the drivers).

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





All of the duplicated code for Blackfin processors and boot modes have been
unified.  After all, the core is the same for all processors, just the
peripheral set differs (which gets handled in the drivers).

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







The patch introduces the CRITICAL feature of POST tests. If the test marked as POST_CRITICAL fails then the alternative, post_critical, boot-command is used. If this command is not defined then U-Boot enters into interactive mode.
2008-03-18T21:24:48+00:00

Yuri Tikhonov
yur@pollux.denx.de

2008-02-04T13:11:03+00:00

b428f6a8c65c5303e5f96db8d24f2f699d94a98c

Signed-off-by: Dmitry Rakhchev <rda@emcraft.com>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>





Signed-off-by: Dmitry Rakhchev <rda@emcraft.com>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>







Remove the __STRICT_ANSI__ check from the __u64/__s64 declaration on 32bit targets.
2008-02-23T08:49:48+00:00

Shinya Kuribayashi
skuribay@ruby.dti.ne.jp

2008-02-23T08:24:16+00:00

b075d74efb70ff68c49a2532f26b56d6703b69c1

----------------------------------------------------------------
Olaf Hering [Wed, 17 Oct 2007 06:27:13 +0000 (23:27 -0700)]

Remove the __STRICT_ANSI__ check from the __u64/__s64 declaration on
32bit targets.

GCC can be made to warn about usage of long long types with ISO C90
(-ansi), but only with -pedantic.  You can write this in a way that even
then it doesn't cause warnings, namely by:

#ifdef __GNUC__
__extension__ typedef __signed__ long long __s64;
__extension__ typedef unsigned long long __u64;
#endif

The __extension__ keyword in front of this switches off any pedantic
warnings for this expression.

Signed-off-by: Olaf Hering <olh@suse.de>
Cc: <linux-arch@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
----------------------------------------------------------------

Signed-off-by: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>





----------------------------------------------------------------
Olaf Hering [Wed, 17 Oct 2007 06:27:13 +0000 (23:27 -0700)]

Remove the __STRICT_ANSI__ check from the __u64/__s64 declaration on
32bit targets.

GCC can be made to warn about usage of long long types with ISO C90
(-ansi), but only with -pedantic.  You can write this in a way that even
then it doesn't cause warnings, namely by:

#ifdef __GNUC__
__extension__ typedef __signed__ long long __s64;
__extension__ typedef unsigned long long __u64;
#endif

The __extension__ keyword in front of this switches off any pedantic
warnings for this expression.

Signed-off-by: Olaf Hering <olh@suse.de>
Cc: <linux-arch@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
----------------------------------------------------------------

Signed-off-by: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>







Coding STyle cleanup.
2008-02-14T23:11:39+00:00

Wolfgang Denk
wd@denx.de

2008-02-14T23:11:39+00:00

7e30f5eac7f07082a7ca77b7d91b944a8d0af6db

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





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