* platform specs (was: PReP spec)
@ 1999-02-12 9:13 Rick Kwan
1999-02-12 22:35 ` Cort Dougan
0 siblings, 1 reply; 6+ messages in thread
From: Rick Kwan @ 1999-02-12 9:13 UTC (permalink / raw)
To: linuxppc-dev
Thanks to Ken Robert's reply to my PReP spec query, I found the
PowerPC FAQ, dated 27 February 1997 at
http://www.mot.com/SPS/PowerPC/library/ppc_faq/ppc_faq.html
and from there, found my way to
ftp://ftp.austin.ibm.com/pub/technology/spec
In this FTP site, the PReP documents are dated Oct 28, 1994, but
there is a "chrp" directory there with documents dated Nov 20, 1995
thru Oct 2, 1996.
In my sporadic reading, it does indeed appear that CHRP has
superceded PReP. However, the above CHRP specs seem either pretty
old or pretty stable. Or am I looking in the wrong place?
>From the FAQ, I also made the journey to Yellowknife, at
http://www.mot.com/SPS/PowerPC/teksupport/refdesigns/yk.html
The design manual is dated 98 Feb 20, and clearly states that it
is a PowerPC/CHRP reference design.
A list of current CHRP machines would indeed be interesting,
if for nothing else, to show the breadth and flexibility of the
architecture. (Or lack thereof.)
--Rick Kwan, Lightsaber Computing
rick.kwan@lightsaber.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: platform specs (was: PReP spec)
1999-02-12 9:13 platform specs (was: PReP spec) Rick Kwan
@ 1999-02-12 22:35 ` Cort Dougan
1999-02-13 0:00 ` Matt Porter
1999-02-13 0:11 ` David Edelsohn
0 siblings, 2 replies; 6+ messages in thread
From: Cort Dougan @ 1999-02-12 22:35 UTC (permalink / raw)
To: Rick Kwan; +Cc: linuxppc-dev
All new rs6000s.
}A list of current CHRP machines would indeed be interesting,
}if for nothing else, to show the breadth and flexibility of the
}architecture. (Or lack thereof.)
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: platform specs (was: PReP spec)
1999-02-12 22:35 ` Cort Dougan
@ 1999-02-13 0:00 ` Matt Porter
1999-02-13 0:55 ` Cort Dougan
1999-02-13 0:11 ` David Edelsohn
1 sibling, 1 reply; 6+ messages in thread
From: Matt Porter @ 1999-02-13 0:00 UTC (permalink / raw)
To: Cort Dougan; +Cc: Rick Kwan, linuxppc-dev
On Fri, 12 Feb 1999, Cort Dougan wrote:
And from the looks of things, all new Motorola boards/systems. Already,
VxWorks BSPs for Moto. boards are easily configured to a CHRP mem map.
Only the firmware defaults to PReP and it is getting dated with its poor
PCI mapping.
> All new rs6000s.
>
> }A list of current CHRP machines would indeed be interesting,
> }if for nothing else, to show the breadth and flexibility of the
> }architecture. (Or lack thereof.)
--
Matt Porter
mmporter@home.com
Unix is a Linux-like operating system.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: platform specs (was: PReP spec)
1999-02-13 0:00 ` Matt Porter
@ 1999-02-13 0:55 ` Cort Dougan
1999-02-13 4:45 ` Matt Porter
0 siblings, 1 reply; 6+ messages in thread
From: Cort Dougan @ 1999-02-13 0:55 UTC (permalink / raw)
To: Matt Porter; +Cc: linuxppc-dev
That's not chrp, though. That's just a chrp memmap. The kernel doesn't
yet deal with a chrp memmap and no-OF. I'd rather stick with prep memmaps
with those boards - it's simple.
}And from the looks of things, all new Motorola boards/systems. Already,
}VxWorks BSPs for Moto. boards are easily configured to a CHRP mem map.
}Only the firmware defaults to PReP and it is getting dated with its poor
}PCI mapping.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: platform specs (was: PReP spec)
1999-02-13 0:55 ` Cort Dougan
@ 1999-02-13 4:45 ` Matt Porter
0 siblings, 0 replies; 6+ messages in thread
From: Matt Porter @ 1999-02-13 4:45 UTC (permalink / raw)
To: Cort Dougan; +Cc: linuxppc-dev
On Fri, 12 Feb 1999, Cort Dougan wrote:
Yes, but from my point of view it is the most important feature. Sticking
with prep memmaps is fine for the current average configuration of a
single or dual cpu setup with a few PCI slaves. When people start putting
together systems with 8-20 CPU's peering over the CPCI bus then PReP
simply won't work because of all the windows that will need to be opened
to map the other processors' board resources in local space. It's good to
keep in mind for the future...
> That's not chrp, though. That's just a chrp memmap. The kernel doesn't
> yet deal with a chrp memmap and no-OF. I'd rather stick with prep memmaps
> with those boards - it's simple.
>
> }And from the looks of things, all new Motorola boards/systems. Already,
> }VxWorks BSPs for Moto. boards are easily configured to a CHRP mem map.
> }Only the firmware defaults to PReP and it is getting dated with its poor
> }PCI mapping.
>
--
Matt Porter
mmporter@home.com
Unix is a Linux-like operating system.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: platform specs (was: PReP spec)
1999-02-12 22:35 ` Cort Dougan
1999-02-13 0:00 ` Matt Porter
@ 1999-02-13 0:11 ` David Edelsohn
1 sibling, 0 replies; 6+ messages in thread
From: David Edelsohn @ 1999-02-13 0:11 UTC (permalink / raw)
To: Cort Dougan; +Cc: Rick Kwan, linuxppc-dev
>>>>> Cort Dougan writes:
Cort> }A list of current CHRP machines would indeed be interesting,
Cort> }if for nothing else, to show the breadth and flexibility of the
Cort> }architecture. (Or lack thereof.)
Cort> All new rs6000s.
Not all new RS/6000 systems are CHRP. I believe that most or all
current 32-bit PowerPC systems are CHRP (43P, F50, etc.). 64-bit Model
S70 might be CHRP. Newest RS/6000 models are not CHRP, including Power3
Model 260.
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-02-13 4:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-02-12 9:13 platform specs (was: PReP spec) Rick Kwan
1999-02-12 22:35 ` Cort Dougan
1999-02-13 0:00 ` Matt Porter
1999-02-13 0:55 ` Cort Dougan
1999-02-13 4:45 ` Matt Porter
1999-02-13 0:11 ` David Edelsohn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).