boot methods

Tom Rini trini at
Sat Nov 3 12:55:47 EST 2001

On Sat, Nov 03, 2001 at 12:13:10PM +1100, Paul Mackerras wrote:
> Tom Rini writes:
> > On Fri, Oct 12, 2001 at 05:32:34PM +1000, Paul Mackerras wrote:
> >
> > > I would like to make a complete list of the methods people use to boot
> > > the PPC/Linux kernel on different platforms.  As a start, here is what
> > > I can think of off the top of my head:
> >
> > All of the 7xx/74xx/8240 boards in _devel boot via zImage.<board> from
> > network/disk/flash, depending.
> Would you mind enumerating them for me?  I would like to have a list
> of the various embedded boards we support in _devel together with the
> value of <board> in the zImage filename, plus what software is used to
> load that into memory.

I this this is mostly correct.  Any of the following, I'm pretty sure,
can also have it thrown in via a BDI.

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
SBS Adirondack	- Uses runlnx, no in-kernel booting bits
SBS K2			.k2			pmon
Zynx 4500		.zx4500			??

Why is the how important?  With the exception of firmware-deficiencies,
the current wrapper doesn't really care what it came from.  And they
usually don't provide much in the way of information about the board
(along the lines of how OF does).

Tom Rini (TR1265)

** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list