All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MIPS: Add board_early_init_f() to init_sequence
Date: Sun, 16 Nov 2008 16:01:38 +0900	[thread overview]
Message-ID: <491FC552.6060102@ruby.dti.ne.jp> (raw)
In-Reply-To: <1226492282-27777-1-git-send-email-sr@denx.de>

Stefan Roese wrote:
> This patch adds the board_early_init_f() call to the MIPS init
> sequence. A weak dummy implementation is also added which can be
> overridden by a board specific version.
> 
> This will be used by the upcoming VCTH board support.
> 
> Signed-off-by: Stefan Roese <sr@denx.de>
> ---
>  lib_mips/board.c |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/lib_mips/board.c b/lib_mips/board.c
> index 77e1cc8..01dda69 100644
> --- a/lib_mips/board.c
> +++ b/lib_mips/board.c
> @@ -70,6 +70,15 @@ static ulong mem_malloc_brk;
>   */
>  unsigned long mips_io_port_base = -1;
>  
> +int __board_early_init_f(void)
> +{
> +	/*
> +	 * Nothing to do in this dummy implementation
> +	 */
> +	return 0;
> +}
> +int board_early_init_f(void) __attribute__((weak, alias("__board_early_init_f")));
> +
>  /*
>   * The Malloc area is immediately below the monitor copy in DRAM
>   */
> @@ -167,6 +176,7 @@ static int init_baudrate (void)
>  typedef int (init_fnc_t) (void);
>  
>  init_fnc_t *init_sequence[] = {
> +	board_early_init_f,
>  	timer_init,
>  	env_init,		/* initialize environment */
>  #ifdef CONFIG_INCA_IP

This is ok.  I don't know why people prefers alias, though :-)

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

  reply	other threads:[~2008-11-16  7:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 12:18 [U-Boot] [PATCH] MIPS: Add board_early_init_f() to init_sequence Stefan Roese
2008-11-16  7:01 ` Shinya Kuribayashi [this message]
2008-11-17 13:56   ` Stefan Roese
2008-11-18  2:41     ` Shinya Kuribayashi
2008-11-17 14:14 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-18 15:00   ` Shinya Kuribayashi
2008-11-18 15:56     ` Stefan Roese

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=491FC552.6060102@ruby.dti.ne.jp \
    --to=skuribay@ruby.dti.ne.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.