Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: root <neuroinc@unidial.com>
To: Ariel Faigon <ariel@cthulhu.engr.sgi.com>
Cc: "linux@engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: Port to R3000 Indigo
Date: Fri, 26 Mar 1999 23:15:09 +0000	[thread overview]
Message-ID: <36FC14FD.46F1279E@unidial.com> (raw)
In-Reply-To: 199903262208.OAA31331@oz.engr.sgi.com

Ariel Faigon wrote:

> As Linus use to say: talk is cheap, show me the code... ;-)

As always!

>
>
> It won't happen by itself, only if someone devotes serious
> time to it.  My personal feeling is that Linux on R3000
> will not happen (there are cheaper and faster old pentium 90's
> out there) but if someone builds it... I've been wrong before.

Are you saying that the effort necessary to port Linux to R3000 Indigo would be
better placed elsewhere?

>
>
> :
> :And I know a group at KSC that's getting rid of a bunch of O2s.  We'd love to
> :grab them and make a nice little Beowulf cluster out of them :-).
> :Unfortunately, we don't have the time at work to do a port :-(
> :
> :> I think it would be very relevant.  My company recently sold around 30
> :> of the R3000 Indigo's.  Just about every person who bought one of these
> :> was interested in the SGI/Linux project and wanted to know if they would
> :> some day be able to run Linux on it.
> :>
>
> --
> Peace, Ariel

The final portion of my original question, is really the most important - are the
hardware specifications/documentation available or are they considered
proprietary?

This issue alone is paramount since it substantially affects the "effort"
necessary to port.

Thanks

- Alan Hoyt -

  parent reply	other threads:[~1999-03-26 23:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-26 20:35 Port to R3000 Indigo Jeremy Parsons
1999-03-26 21:46 ` tom
1999-03-26 22:08   ` Ariel Faigon
1999-03-26 22:21     ` Martin Mielke
1999-03-26 23:15     ` root [this message]
1999-03-27  0:39       ` Ariel Faigon
1999-03-27  0:39         ` Ariel Faigon
1999-03-29 23:38         ` Alan Hoyt
1999-03-30  8:53           ` Ariel Faigon
1999-03-30  8:53             ` Ariel Faigon
1999-03-30 15:29             ` Alan Hoyt
1999-03-31 16:18             ` Mike Shaver
1999-03-27  1:45   ` Theodoros Nikitopoulos
1999-03-26 23:52     ` William J. Earl
1999-03-29 15:09       ` Address of PROMBLOCK on 64 bit systems Honza Pazdziora
1999-03-27  3:46     ` Port to R3000 Indigo Steve Martin
1999-03-26 22:21 ` Jurgen Kramer
  -- strict thread matches above, loose matches on Subject: below --
1999-03-31  0:25 Alan Hoyt
1999-03-31  1:34 ` Mark A. Zottola
1999-03-31  2:33   ` William J. Earl

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=36FC14FD.46F1279E@unidial.com \
    --to=neuroinc@unidial.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@cthulhu.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