From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: introduce arch_early_init_r()
Date: Tue, 3 Apr 2012 00:08:33 +0200 [thread overview]
Message-ID: <201204030008.33769.marex@denx.de> (raw)
In-Reply-To: <20120402220157.GB32655@bill-the-cat>
Dear Tom Rini,
> On Tue, Apr 03, 2012 at 12:00:31AM +0200, Marek Vasut wrote:
> > Dear Tom Rini,
> >
> > > On Mon, Apr 02, 2012 at 06:19:45PM -0300, Fabio Estevam wrote:
> > > > Introduce arch_early_init_r() function, which can be useful for doing
> > > > early initialization after relocation has happened.
> > > >
> > > > Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> > >
> > > Perhaps I just overlooked earlier conversations, but why not just do
> > > this in board_init() ?
> >
> > Because we have multiple boards and they all need it.
>
> And you aren't architectured with a common board_init() over the family
> (would there be little to no duplication)? This is what we do in
> various TI families.
Common board_init() ? How would you then do the actual distinct per-board init?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-04-02 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 21:19 [U-Boot] [PATCH 1/2] ARM: introduce arch_early_init_r() Fabio Estevam
2012-04-02 21:19 ` [U-Boot] [PATCH 2/2] mmc: mxsmmc: Fix operation with DMA Fabio Estevam
2012-04-02 21:42 ` [U-Boot] [PATCH 1/2] ARM: introduce arch_early_init_r() Tom Rini
2012-04-02 22:00 ` Marek Vasut
2012-04-02 22:01 ` Tom Rini
2012-04-02 22:08 ` Marek Vasut [this message]
2012-04-02 22:13 ` Tom Rini
2012-04-02 22:15 ` Tom Rini
2012-04-02 23:05 ` Graeme Russ
2012-04-06 0:30 ` Marek Vasut
2012-04-06 0:33 ` Fabio Estevam
2012-04-06 1:04 ` Marek Vasut
2012-07-07 11:53 ` Albert ARIBAUD
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=201204030008.33769.marex@denx.de \
--to=marek.vasut@gmail.com \
--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