On Tue, Apr 03, 2012 at 12:08:33AM +0200, Marek Vasut wrote:
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?
Pah, mis-recalled things, sorry. We have a pre-relocation hook that's common per-family (lowlevel_init (generic) -> s_init (TI generic)).