From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Schwingen <rincewind@discworld.dascon.de>
Date: Sun, 09 Dec 2007 17:38:13 +0100
Subject: [U-Boot-Users] [PATCH] ARM: add support
 of	CONFIG_LAST_STAGE_INIT for arm
In-Reply-To: <20071209145042.C7E41247F5@gemini.denx.de>
References: <20071209145042.C7E41247F5@gemini.denx.de>
Message-ID: <475C19F5.4090507@discworld.dascon.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:
>>  #endif
>>  	eth_initialize(gd->bd);
>>  #endif
>> +#ifdef CONFIG_LAST_STAGE_INIT
>> +	/*
>> +	 * Some parts can be only initialized if all others (like
>> +	 * Interrupts) are up and running (i.e. the PC-style ISA
>> +	 * keyboard).
>> +	 */
>> +	last_stage_init ();
>> +#endif
> Please, not yet another such thing.
>
> Is there any specific reason why you cannot use any of the existing
> entry points, like for example board_late_init() ?
>   
In my case, I need board-specific init code for the ethernet 
PHY/Switches, which needs to run after eth_inizialize, so 
board_late_init (at least on arm) is still too early.

If we could move board_late_init after eth_initialize (ie. directly 
before calling main_loop), that would work in my case, and would remove 
the necessity for my reset_phy patch.

cu
Michael