boot methods
Tom Rini
trini at kernel.crashing.org
Sun Nov 4 02:15:53 EST 2001
On Sat, Nov 03, 2001 at 10:45:37AM +0100, Wolfgang Denk wrote:
> In message <20011102185547.B29932 at cpe-24-221-152-185.az.sprintbbd.net> you wrote:
> >
> > Vendor Extension How
> > IBM Spruce .spruce ???
> > Force PowerCore .pcore PowerBoot (Force firmware)
> > Force PowerPMC 250 .pcore PowerBoot
> > M.E.N. F1 .menf1 ??? (Probably custom fw).
> > Motorola LoPEC .pplus/.bugboot[1] PPCBUG
> > Motorola MCPN765 same same
> > Motorola MVME5100 same same
> > Motorola PrPMC750 same same
> > Motorola PrPMC750 same same
> > Motorola Sandpoint .sandpoint DINK32
[snip]
[1]: .bugboot is for images in flash.
> > Why is the how important? With the exception of firmware-deficiencies,
> > the current wrapper doesn't really care what it came from. And they
>
> ...or there is no wrapper at all.
But that's going to be much of an option. I think we want to enforce
some wrapper, so that things like PPCBoot aren't effected by internal
changes. And I don't think the PPCBoot wrapper needs to be all that big
either. I do need to sit down and verify this, but a PPCBoot wrapper
could be as minimal as taking a current bd_t structure and converting it
to bi_recs. No duplicated serial, et al.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev
mailing list