From: Mike McDonald <mikemac@mikemac.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: MIPS platform recommendations
Date: Sat, 27 Jan 2001 14:48:46 -0800 [thread overview]
Message-ID: <200101272248.OAA05566@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Fri, 26 Jan 2001 10:47:13 +0100." <00cc01c0877c$fbc8a8e0$0deca8c0@Ulysses>
>From: "Kevin D. Kissell" <kevink@mips.com>
>To: "John Van Horne" <JohnVan.Horne@cosinecom.com>, <linux-mips@oss.sgi.com>
>Subject: Re: MIPS platform recommendations
>Date: Fri, 26 Jan 2001 10:47:13 +0100
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_00C7_01C08785.57A97F60
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>MIPS platform recommendationsPersonally, I use an Algorithmics P-5064 =
>board
>with an R5260 CPU for this sort of thing. It's an
>ATX board that I've got bolted into a cheapo
>generic ATX enclosure on my lab network. They
>also have an RM7000 CPU module available.
>I'm running the MIPS 2.2.x port on it, however,
>not 2.4. See www.algor.co.uk for info on the
>board.
At (US) $3900 a copy, you have deeper pockets than I do. MUCH
deeper! (http://www.algor.co.uk/algor/info/p5064-benefits.html)
Mike McDonald
mikemac@mikemac.com
prev parent reply other threads:[~2001-01-27 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 19:23 MIPS platform recommendations John Van Horne
2001-01-24 20:30 ` Pete Popov
2001-01-25 0:17 ` Ralf Baechle
2001-01-25 1:13 ` Pete Popov
2001-01-26 9:47 ` Kevin D. Kissell
2001-01-26 9:47 ` Kevin D. Kissell
2001-01-27 22:48 ` Mike McDonald [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=200101272248.OAA05566@saturn.mikemac.com \
--to=mikemac@mikemac.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
/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