Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alistair Lambie <alambie@rock.csd.sgi.com>
To: fisher@sgi.com
Cc: ralf@oss.sgi.com, kevink@mips.com, linux@hollywood.engr.sgi.com,
	William Fisher <fisher@hollywood.engr.sgi.com>
Subject: Re: Question for David Miller or anyone else about R6000 code
Date: Wed, 08 Dec 1999 17:30:49 +1300	[thread overview]
Message-ID: <384DDEF9.E3BE1F10@csd.sgi.com> (raw)
In-Reply-To: 199912080313.TAA24823@hollywood.engr.sgi.com

William Fisher wrote:
> 
> >
> > On Mon, Dec 06, 1999 at 10:58:10AM +0100, Kevin D. Kissell wrote:
> >
> > > I'm working on cleaning up and enhancing the
> > > MIPS/Linux code to support the new families
> > > of CPUs coming out of MIPS Technologies Inc.
> > > In doing so, I've come across and fixed a number
> > > of bugs, most of which I've also passed back to
> > > Ralf Baechle for integration with the moving
> > > target at linux.sgi.com.   But I came across
> > > something this morning that, while not a problem
> > > for us, puzzles me.   In arch/mips/mm/r6000.c,
> > > which has your name on it, there is a compiler
> > > directive to use MIPS III instructions, and the
> > > resulting code does indeed end up containing
> > > 64-bit (daddiu, etc.) instructions.   I've never
> > > actually programmed an R6000, but all of the
> > > information I have on that processor indicates
> > > that it is a MIPS II, 32-bit design, and that those
> > > instructions should therefore cause exceptions.
> > >
> > > Am I mistaken, or is that directive a bug?
> >
> > It obviously is.  The R6000 code isn't supposed to work and given that
> > currently none of the Linux/MIPS hackers has a) R6000 documentation and
> > b) an R6000 machine an R6000 port ever happening is highly unprobable.
> > As the result of this I think I'm going to just burry the R6000 support
> > and while I'm at it also the R8000.
> >
> >   Ralf
> >
>         Since the R6000 was an ECL machine produced in late 1992, just
>         before the MIPS/SGI merger. There were only a few machines sold
>         and the machine was designed to be a Fortran FP specialist.
> 
>         Hence the R6000 is long since dead. We still have the MIPS risc/os 5.01
>         operating system source code, so if anybody has lots of free cycles
>         to waste, I'm sure we can send them locore.
> 

Don't forget CDC used the R6000 and ramped it to 90MHz.  They also got
it going in an SMP configuration with 4 processors from what I can
remember.  I guess it is possible that someone could actually want to
burn some cycles on this, although they had better have a cheap source
of power and good airconditioning :-)

Alistair

-- 
Alistair Lambie                                alambie@csd.sgi.com
SGI Global Product Support
Level 5, Cigna House,                                M/S: INZ-3780
PO Box 24 093,                                  Ph: +64-4-494 6325
40 Mercer St, Wellington,                      Fax: +64-4-494 6321
New Zealand                                 Mobile: +64-21-635 262

  parent reply	other threads:[~1999-12-08  4:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06  9:58 Question for David Miller or anyone else about R6000 code Kevin D. Kissell
1999-12-05 10:34 ` Marc Esipovich
1999-12-06 11:28 ` Ralf Baechle
1999-12-08  3:13   ` William Fisher
1999-12-08  3:13     ` William Fisher
1999-12-08  4:30     ` Alistair Lambie [this message]
1999-12-08 11:21       ` Ralf Baechle
1999-12-08  6:00     ` William J. Earl
1999-12-08  6:00       ` William J. Earl
  -- strict thread matches above, loose matches on Subject: below --
1999-12-06 11:41 Kevin D. Kissell
1999-12-06 12:09 ` Ralf Baechle

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=384DDEF9.E3BE1F10@csd.sgi.com \
    --to=alambie@rock.csd.sgi.com \
    --cc=fisher@hollywood.engr.sgi.com \
    --cc=fisher@sgi.com \
    --cc=kevink@mips.com \
    --cc=linux@hollywood.engr.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