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.
[snip]
Along those lines, I have been thinking that it would be good if the
wrapper built a data structure describing the hardware in the system,
particularly things like:
- the amount of RAM and any holes
- type and register addresses for PCI host bus adaptors
- ditto for interrupt controllers
- interrupt mapping
One thing we have to keep in mind is what's required and what's
optional. On some machines like pmac, we have a nice firmware that sets
everything up for us and is rather 'nice' to talk with. On other boards
things are setup just enough by the firmware that we can load some bits
and with luck fix firmware 'issues' (see simple/head.S). If we have to
find out things like RAM size from the piggyback loader, it's going to
bloat it a good deal. We'd need, roughly to throw in mpc10x_common.c
into both the piggyback and the kernel.
If we want to keep all of this information around after init, it
wouldn't be hard to fill out the struct I suppose..
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Paul Mackerras <hidden> Date: 2001-11-03 01:13:10
Tom Rini writes:
On Fri, Oct 12, 2001 at 05:32:34PM +1000, Paul Mackerras wrote:
quoted
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.
Thanks,
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Sat, Nov 03, 2001 at 12:13:10PM +1100, Paul Mackerras wrote:
Tom Rini writes:
quoted
On Fri, Oct 12, 2001 at 05:32:34PM +1000, Paul Mackerras wrote:
quoted
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)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/