On 7/3/07, Andrew Dyer amdyer@gmail.com wrote:
I would like to see the 'second stage' of u-boot be made more modular. I imagine a set of basic code (console, environment, loader, storage driver) would get loaded first and additional commands and drivers could be stored as compressed uImages and loaded as needed and chained onto the list of valid commands/functions. This shouldn't be allowed to get too out of hand (no automatic dependency resolution, autoloading, or anything like that :-)
Doesn't this already kind of exist in the form of u-boot applications?
It might be nice to have something like tinderbox - a machine churning through building all of the supported platforms based on a top of git stable and/or testing branch and have a web status. It would make it easier to test system wide changes if the developer doesn't have all of the toolchains on their machines and would help keep platforms code from getting 'stale'.
I agree 100%. The biggest problem here is not having anyone interested and with enough time to write and maintain it. Also, since there are so many board ports involved, the tinderbox should be somewhat distributed so that the builds can also be tested on the various boards developer have scattered about the globe. (ie. ideally it should be dead easy for someone to volunteer time on one of their boards to be part of the tinderbox process)
Is u-boot big enough to have a 'janitor'?
Yes, are you volunteering? :-D
Cheers, g.