From: Florian Lohoff <flo@rfc822.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC/MCA RS/6000 port ?
Date: Mon, 20 Mar 2000 20:54:53 +0100 [thread overview]
Message-ID: <20000320205453.G1363@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.HPX.4.10.10003200116330.28648-100000@gra-ux1.iram.es>; from Gabriel Paubert on Mon, Mar 20, 2000 at 01:20:32AM +0100
On Mon, Mar 20, 2000 at 01:20:32AM +0100, Gabriel Paubert wrote:
> > Model (C20/C10) - PPC 601 or 604 depending on the
> > CPU Module and ~4-5 MCA Slots
>
> This is a recurring question on this list which comes up every few months.
> I don't think anybody is working on a port due to the lack of HW
> documentation and the probably odd implementation (there must be reason
> for the so called direct store segments supported by the MMU of early PPC
> processors).
But as i understood - The 601 is supported - If it isnt there are
still machines left - The Model C10/C20 with a 604 CPU Module.
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-20 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-19 20:36 PPC/MCA RS/6000 port ? Florian Lohoff
2000-03-20 0:20 ` Gabriel Paubert
2000-03-20 2:57 ` David Edelsohn
2000-03-20 19:53 ` Florian Lohoff
2000-03-20 19:59 ` David Edelsohn
2000-03-20 20:05 ` PPC601 support Hollis R Blanchard
2000-03-20 20:24 ` Justin Shore
2000-03-21 1:40 ` PPC/MCA RS/6000 port ? David A. Gatwood
2000-03-20 20:50 ` Gabriel Paubert
2000-03-20 20:45 ` Gabriel Paubert
2000-03-21 12:50 ` Dave Weis
2000-03-21 14:30 ` Gabriel Paubert
2000-03-21 20:45 ` Dave Weis
2000-03-20 19:54 ` Florian Lohoff [this message]
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=20000320205453.G1363@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).