public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MIPS: Add board_early_init_f() to init_sequence
Date: Mon, 17 Nov 2008 14:56:13 +0100	[thread overview]
Message-ID: <200811171456.13382.sr@denx.de> (raw)
In-Reply-To: <491FC552.6060102@ruby.dti.ne.jp>

On Sunday 16 November 2008, Shinya Kuribayashi wrote:
> > +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 :-)

Just because we don't need the ugly #ifdef's by using weak aliases. It has 
some drawbacks of course but in general the resulting source code 
looks "cleaner".

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-11-17 13:56 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
2008-11-17 13:56   ` Stefan Roese [this message]
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=200811171456.13382.sr@denx.de \
    --to=sr@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