Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Greg Johnson <gjohnson@superweasel.com>, linux-mips@oss.sgi.com
Subject: Re: Linux on a 100MHz r4000 indy?
Date: Tue, 17 Jul 2001 09:06:24 +0200	[thread overview]
Message-ID: <20010717090624.A2471@bacchus.dhis.org> (raw)
In-Reply-To: <001301c10e84$570805a0$0deca8c0@Ulysses>; from kevink@mips.com on Tue, Jul 17, 2001 at 07:50:00AM +0200

On Tue, Jul 17, 2001 at 07:50:00AM +0200, Kevin D. Kissell wrote:

> I don't have access to old R4000 revision data, and I'll take your
> word for the errata applicable to rev 0422.

There is a cool site on the internet to get such data.  It's
http://www.mips.com/Documentation/R4000_3.0_2.2_PC_SC_errata.pdf :-)

> A am a *little* surprised that such early parts found their way into
> Indys, since the Indy was not the first R4000 platform (I believe that
> honor belongs to the "Crimson" graphics workstations), but it's certainly
> possible.

Agreed.  So far I thought the oldest CPU module we have to worry about
is v3.0.

If somebody has an old 2.2 CPU module for an Indy lying around which he
wants to send to me for debugging such stuff ...

  Ralf

  parent reply	other threads:[~2001-07-17  7:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 20:37 Linux on a 100MHz r4000 indy? Greg Johnson
2001-07-17  1:20 ` Ralf Baechle
2001-07-17  2:39   ` Greg Johnson
2001-07-17  3:00     ` Ralf Baechle
2001-07-17  3:08       ` Greg Johnson
2001-07-17  5:50       ` Kevin D. Kissell
2001-07-17  5:50         ` Kevin D. Kissell
2001-07-17  7:06         ` Ralf Baechle [this message]
2001-07-17  7:28           ` Geert Uytterhoeven
2001-07-17  8:16             ` Maciej W. Rozycki

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=20010717090624.A2471@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=gjohnson@superweasel.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