[U-Boot] [RFC] Driver model

[Albert ARIBAUD <albert.aribaud@free.fr>]

Le 24/09/2010 19:35, Wolfgang Denk a ?crit :
> Dear Marek Vasut,
>
> In message<201009241737.27335.marek.vasut@gmail.com>  you wrote:
>>
>>> Using the DT for run-time configuration of U-Boot would be especially
>>> interesting. Assume: a single U-Boot image for all - say - OMAP3
>>> boards...
>>
>> This looks very cool. I thought about this and I came to a further idea:
>> * Make "minimal" u-boot that'd be independent of DTree
>> * Upon setting variable "fdt" to an address of the DTree, enable remaining
>> components of uboot
>>
>> The second point would allow booting a platform in case the DTree was faulty. Or
>> we can have a known-good DTree and a variable that'd allow to override it, that
>> might be even better.
>
> We will probably need something like that anyway - the "minimal
> configuration" being largely what is running before relocation, the
> "full configuration" when we have full access to normal resources.
>
> Best regards,
>
> Wolfgang Denk

Stop me if I'm wrong, but basically this would imply that u-boot be 
built with support for the largest possible device combination, thus be 
rather big, right? I hope the ability to trim it down u-boot to a 
minimum is retained, though, i.e. be able to choose between a 
one-size-fits-all binary that will run on anything *or* a tight fit that 
will run only on a given platform with minimal footprint (or anything 
in-between, actually).

Amicalement,
-- 
Albert.