[EMAIL PROTECTED] (Eric W. Biederman) writes:

> Ronald G Minnich <[EMAIL PROTECTED]> writes:
> 
> > On 26 Jun 2002, Eric W. Biederman wrote:
> > 
> > > I don't see a reason to go 64bit, or to have multiple types.
> > > I'm trying to figure out what the best way to allocate it is.  Either
> > > to statically allocate the array in hardwaremain.c (with the size set in
> > > the config file) or to actually pass it back from the sizeram function.
> > >
> > > Probably the latter, probably already have to many config options.
> > 
> > definitely the latter. Besides, we kind of have an malloc() :)
> 
> But we know the size at compile time.  I have gone for an ordered
> null terminated array.  After I implement it for my port I will
> see how it works out for the others...
> 
> Anyway I'm implementing as we speak.

The truly hard part is the rewrite of mtrr.c so it automatically does
the write thing.

Eric

Reply via email to