Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg Johnson <gjohnson@superweasel.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Linux on a 100MHz r4000 indy?
Date: Mon, 16 Jul 2001 22:39:02 -0400	[thread overview]
Message-ID: <20010716223902.A16351@superweasel.com> (raw)
In-Reply-To: <20010717032055.A1236@bacchus.dhis.org>

On Tue, Jul 17, 2001 at 03:20:55AM +0200, Ralf Baechle wrote:
> On Mon, Jul 16, 2001 at 04:37:12PM -0400, Greg Johnson wrote:
> 
> > I also have another indy with a 175MHz r4400.  This machine seems to
> > work fine even without the fast-sysmips patch.  
> 
> This could be explained if you have different libraries, the one compiled for
> MIPS II, the other one only for MIPS I on these two systems.  Sure you're
> running the very same binaries?

They're the same.

> Depends.  The older R4000s were really buggy silicon and we don't
> have all the workarounds needed to keep them happy.  So in theory if
> circumstances are just right that can explain why you have so much
> fun with the R4000 machine.

Interesting.

> When the kernel is booting it prints a a line "CPU revision is: xxx"
> where xxx is a 8 digit hex number.  What number?

For the r4000 indy:

ARCH: SGI-IP22
PROMLIB: ARC firmware Version 1 Revision 10
CPU: MIPS-R4000 FPU<MIPS-R4000FPC> ICACHE DCACHE SCACHE 
Loading R4000 MMU routines.
CPU revision is: 00000422
Primary instruction cache 8kb, linesize 16 bytes.
Primary data cache 8kb, linesize 16 bytes.
Secondary cache sized at 1024K linesize 128 bytes.

For the r4400 indy:

ARCH: SGI-IP22
PROMLIB: ARC firmware Version 1 Revision 10
CPU: MIPS-R4400 FPU<MIPS-R4400FPC> ICACHE DCACHE SCACHE 
Loading R4000 MMU routines.
CPU revision is: 00000460
Primary instruction cache 16kb, linesize 16 bytes.
Primary data cache 16kb, linesize 16 bytes.
Secondary cache sized at 1024K linesize 128 bytes.


Thanks,

Greg

  reply	other threads:[~2001-07-17  2:41 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 [this message]
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
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=20010716223902.A16351@superweasel.com \
    --to=gjohnson@superweasel.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@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