"Ian" <[EMAIL PROTECTED]> writes:
> > Hmm. As long as you have the information to describe your hardware I
> > don't see the problem. What is the problem with rewriting memory?
> Not rewriting it, reinitializing it ... jumping down to the controller and
> telling it
>
> you have 4 x 64Mbyte sticks installed ... upon that initialisation (from what I
> understand of it all), your RAM gets blanked.
O.k. The ram reinitialization, click. Yes this is the one thing you
can't do from linux, and I don't think this task would be sane to do.
In particular the linux kernel is just to darn big to fit even into L2
cache although the compressed form comes pretty close.
> > I do it everyday when I boot linux from linux, and I have no problems.
> Not at this level though ...
>
> > No. With older kernels that don't have support for doing the
> > intialization themselves I can see it happening.
> Older kernels shouldn't be a problem with what I'm talking about ... if Day-1
> Kern+LB comes with either Kern-to-Kern boot detection or Boot Param knowledge
> or Hardware-pre-config detection then backward compatibility with such functions
>
> won't ever be an issue (as it doesn't affect currently un-LinuxBios-ed kernels).
>
>
> Its just the idea of a ruthless "I'm here, now lets start with that memory"
> attitude from
>
> the kernel that I think will be a wee bit problematic .. when the universe is
> considered.
O.k. I think I follow the concern. The plan it to push a maximal
amount of stuff onto linux. However the plan is not to do it all in
linux. In particular I don't see linux doing memory init or loading
itself out of flash. LinuxBIOS will just be very lean & mean, not a
part of the kernel proper.
Eric
