From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] POST cleanup.
Date: Mon, 10 May 2010 13:17:05 +0200 [thread overview]
Message-ID: <m2pr1480r2.fsf@ohwell.denx.de> (raw)
In-Reply-To: <394e9c9847defc6321a52ef052987fabb6c95f31.1273418079.git.michael.zaidman@gmail.com> (Michael Zaidman's message of "Sun, 9 May 2010 18:27:10 +0300")
Hi Michael,
> Combine previously submitted POST cleanup patch series
> into single patch. Fix plain POST support introduced recently
> for mpc812x arch.
>
> - Revives POST for blackfin arch;
> - Removes redundant code:
> arch/blackfin/lib/post.c
> board/ssv/common/post.c
> arch/powerpc/cpu/ppc4xx/commproc.c
> arch/powerpc/cpu/mpc512x/common.c
> - fixes up the post_word_{load|store} usage;
Thanks for the big work.
It would have been really nice if you put the maintainers on CC (simply
include a CC: ... in the patch git-send-email does the rest) of the
boards that you change config files. This way they knew that there was
a change which they should test and ack.
For the powerpc parts, you have my
Acked-by: Detlev Zundel <dzu@denx.de>
> diff --git a/board/barco/barco.c b/board/barco/barco.c
> index c5fe8c4..2d01f1b 100644
> --- a/board/barco/barco.c
> +++ b/board/barco/barco.c
> @@ -348,12 +348,3 @@ int serial_tstc (void)
> {
> return 0;
> }
> -
> -unsigned long post_word_load (void)
> -{
> - return 0l;
> -}
> -void post_word_store (unsigned long val)
> -{
> - return;
> -}
This never worked :) The config file has no trace of any POST, so the
change you do is pretty useless:
> diff --git a/include/configs/barco.h b/include/configs/barco.h
> index e00f84a..b1af701 100644
> --- a/include/configs/barco.h
> +++ b/include/configs/barco.h
> @@ -136,6 +136,8 @@
> #define CONFIG_LOGBUFFER
> #ifdef CONFIG_LOGBUFFER
> #define CONFIG_SYS_STDOUT_ADDR 0x1FFC000
> +#define CONFIG_SYS_POST_WORD_ADDR \
> + (CONFIG_SYS_SDRAM_BASE + CONFIG_SYS_MAX_RAM_SIZE - 4)
> #else
> #define CONFIG_SYS_STDOUT_ADDR 0x2B9000
> #endif
But then again, it doesn't matter.
Cheers
Detlev
--
If you currently have a 32-bit UNIX system, you are advised to
trade it in for a 64-bit one sometime before the year 2106.
-- Andrew S. Tanenbaum: Modern Operating Systems, 2nd Edition
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-05-10 11:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 10:38 [U-Boot] [PATCH v3] POST cleanup v3 (incremental) Michael Zaidman
2010-05-06 21:42 ` Wolfgang Denk
2010-05-09 15:27 ` [U-Boot] [PATCH v4] POST cleanup Michael Zaidman
2010-05-10 11:17 ` Detlev Zundel [this message]
2010-05-10 11:39 ` Michael Zaidman
2010-05-12 12:02 ` Detlev Zundel
2010-05-12 12:49 ` Michael Zaidman
2010-06-27 14:00 ` Michael Zaidman
2010-05-10 12:12 ` Michael Zaidman
2010-05-10 13:33 ` [U-Boot] [PATCH v5] " Michael Zaidman
2010-06-29 19:51 ` Wolfgang Denk
2010-06-30 16:16 ` [U-Boot] [PATCH v6] " Michael Zaidman
2010-08-08 6:53 ` Michael Zaidman
2010-08-08 20:30 ` Wolfgang Denk
2010-08-10 13:37 ` Michael Zaidman
2010-09-20 6:51 ` [U-Boot] [PATCH V7] " Michael Zaidman
2010-09-21 19:40 ` Wolfgang Denk
2010-10-26 21:09 ` Wolfgang Denk
2010-11-13 22:55 ` Wolfgang Denk
2010-11-21 12:34 ` Michael Zaidman
2010-12-06 8:00 ` Michael Zaidman
2010-05-10 11:51 ` [U-Boot] [PATCH v4] " Anatolij Gustschin
2010-05-10 11:55 ` Michael Zaidman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pr1480r2.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox