Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alistair Lambie <alambie@rock.csd.sgi.com>
Cc: fisher@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, 8 Dec 1999 09:21:12 -0200	[thread overview]
Message-ID: <19991208092112.F10331@uni-koblenz.de> (raw)
In-Reply-To: <384DDEF9.E3BE1F10@csd.sgi.com>

On Wed, Dec 08, 1999 at 05:30:49PM +1300, Alistair Lambie wrote:

> 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 :-)

At one time some Linux/m68k hacker was seriously looking into porting
Linux to a 3-CPU 256mb CDC which at that time was used as
ftp.uni-erlangen.de.

As usual the largest problem was technical documentation for the machine
and the CPU; the R6k is covered very badly by the freely available
documentation.

  Ralf

  reply	other threads:[~1999-12-08 11:22 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
1999-12-08 11:21       ` Ralf Baechle [this message]
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=19991208092112.F10331@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=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 \
    /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