Ram initialization and small c.

[Ronald G. Minnich]

On 13 Feb 2003, Eric W. Biederman wrote:

> The basic layout I am looking at, is to have some kind of list of hardware
> in the code.  And then for each piece of hardware call an initialization
> function.  This has the potential to replace a lot of code in the
> current hardwaremain.c  Handling initialization order is an
> interesting problem I have not tackled yet.

I think the superio stuff is one possible way. I've found that three
passes covers the case for superio, and actually for southbridge. 

For the multiple northbridge case did you want to discover northbridges 
dynamically or continue to specify it in a config file.

The _fixup stuff goes away with the three pass approach, I think.

I'd like to hash this out a bit on the list the way I've hashed out other 
approaches in the past (config tool, new superio, etc.) to see if we can't 
scare up good ideas from other people.

ron