From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Becky Bruce <becky.bruce@freescale.com>,
linuxppc64-dev@ozlabs.org
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Thu, 11 Aug 2005 21:14:43 -0700 [thread overview]
Message-ID: <20050812041443.GC3187@smtp.west.cox.net> (raw)
In-Reply-To: <17148.7234.193140.997481@cargo.ozlabs.ibm.com>
On Fri, Aug 12, 2005 at 01:49:22PM +1000, Paul Mackerras wrote:
> Tom Rini writes:
>
> > I'm a bit ppc64-ignorant, but isn't 'pSeries' just a regular
> > OpenFirmware-containing ppc64 box (like Maple) ? How about just 9xx/
>
> Ummm, no, not exactly. The distinctive thing about pSeries is the
> hypervisor interfaces. And in fact most pSeries boxes aren't
> 970-based, rather POWER4/4+/5. If you want to generalize, we could
> call the directory "papr" (for Power Architecture Platform
> Requirements, the name of the document that describes the pSeries
> platforms) rather than pSeries, but I suspect that would just confuse
> people. :)
Ok. How about 9xx/ instead of classic64 ?
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-08-12 4:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:45 RFC: proposed arch/powerpc directory structure Becky Bruce
2005-08-10 17:01 ` Dan Malek
2005-08-10 21:35 ` John W. Linville
2005-08-11 0:09 ` Stephen Rothwell
2005-08-11 1:10 ` Olof Johansson
2005-08-11 19:59 ` Tom Rini
2005-08-11 20:13 ` Kumar Gala
2005-08-11 20:18 ` Tom Rini
2005-08-11 22:41 ` Becky Bruce
2005-08-11 23:07 ` Kumar Gala
2005-08-11 23:19 ` Tom Rini
2005-08-12 2:34 ` Kumar Gala
2005-08-12 3:38 ` Tom Rini
2005-08-11 23:29 ` Dan Malek
2005-08-12 2:09 ` Josh Boyer
2005-08-12 3:49 ` Paul Mackerras
2005-08-12 4:14 ` Tom Rini [this message]
2005-08-15 18:25 ` Segher Boessenkool
2005-08-11 20:25 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050812041443.GC3187@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=becky.bruce@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).