[U-Boot] [RFC] New init sequence processing without init_sequence array

[Mike Frysinger]

On Monday, August 22, 2011 16:10:23 Wolfgang Denk wrote:
> 3. Hardware initialization in inherently very much hardware depen-
>    dent ;-)  We have some boards where PCI must be initialized early
>    because it is needed to access some other peripherals like memory.
>    And we have other boards where PCI can only be initialized late
>    because it depends on a lot of other functions that must be working
>    first.
> 
>    I explained this a number of times before: the current code was
>    designed to allow even for completely board specific init
>    sequences, by simply adding #define for the list of init functions
>    to the board config file - see for example here:
> 
>    http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/33951/focus=36436
> 
>    http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/72131/focus=72136
> 
>    If you look at the current code - heavily larded with #ifdefs of
>    all shapes and colors - I cannot see any good way to transform this
>    into an initcall (and thus sequence number based) implementation.
>    Do you have any specific ideas how to address this?

if the funcs get merged by the linker script, the board still has full control 
over the init order by writing their own linker script
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110822/086cf11b/attachment.pgp