Re: boot methods

In message [off-list ref] 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

also: Sandpoint         .PPCBoot		PPCBoot

SBS Adirondack        - Uses runlnx, no in-kernel booting bits
SBS K2                .k2                     pmon
Zynx 4500             .zx4500                 ??

add:

  "CU824" Board (8240)
  Microsys Electronics	.PPCBoot		PPCBoot

  MOUSSE Board (8240)	.PPCBoot		PPCBoot

  EVB64260 (74xx)	.PPCBoot		PPCBoot

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.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
You are only young once, but you can stay immature indefinitely.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

On Sat, Nov 03, 2001 at 10:45:37AM +0100, Wolfgang Denk wrote:

In message [off-list ref] you wrote:

quoted

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.

quoted

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/