Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: olson@anchor.engr.sgi.com (Dave Olson)
To: sparker@taz.cs.utah.edu (Steven G. Parker)
Cc: ralf@uni-koblenz.de, andrewb@uab.edu, linux-smp@vger.rutgers.edu,
	linux@cthulhu.engr.sgi.com
Subject: Re: Linux on an SGI Challenge L
Date: Thu, 10 Dec 1998 08:21:47 -0800 (PST)	[thread overview]
Message-ID: <199812101621.IAA84751@anchor.engr.sgi.com> (raw)
In-Reply-To: <9812100859.ZM7179@taz.cs.utah.edu> from "Steven G. Parker" at "Dec 10, 98 08:59:11 am"

Steven G. Parker wrote: 
|  On Dec 10,  4:36pm, ralf@uni-koblenz.de wrote:
|  > > Anyone care to make any comments on porting Linux to an SGI Challenge L
|  > > machine w/ (4) R4400 processors?  Am I crazy to even attempt this?
|  >
|  > You're not crazy, after all Linux is already running on bigger iron and
|  > about to run on Sun's E10000.  However you should checkout again what
|  > hardware you actually have on your system.  A Challenge L is mostly like
|  > an Indy (which is supported), that is strictly uniprocessor.  So
|  > your system either is not a multiprocessor system or not a Challenge L.
|  
|  Actually, the Indy system is a Challenge S.  The Indigo^2 system is
|  a Challenge M.   The Challenge L is the desk-side system and can indeed
|  support multiple processors.
|  
|  I can only comment on the model line - not on whether you are crazy or not :)

The hardware is radically different.  The only shared item is the cpu,
and even it's used in a fairly different way.  indy w/o graphics as
challenge S, etc. is strictly a marketing idea.

It's clearly doable, but you need a whole new set of hardware specs.

Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

WARNING: multiple messages have this Message-ID (diff)
From: olson@anchor.engr.sgi.com (Dave Olson)
To: "Steven G. Parker" <sparker@taz.cs.utah.edu>
Cc: ralf@uni-koblenz.de, andrewb@uab.edu, linux-smp@vger.rutgers.edu,
	linux@cthulhu.engr.sgi.com
Subject: Re: Linux on an SGI Challenge L
Date: Thu, 10 Dec 1998 08:21:47 -0800 (PST)	[thread overview]
Message-ID: <199812101621.IAA84751@anchor.engr.sgi.com> (raw)
Message-ID: <19981210162147.Ztml6YZ3fZNG_VJv7pHIeka6CjtfVVfshE7a2Czuls8@z> (raw)
In-Reply-To: <9812100859.ZM7179@taz.cs.utah.edu> from "Steven G. Parker" at "Dec 10, 98 08:59:11 am"

Steven G. Parker wrote: 
|  On Dec 10,  4:36pm, ralf@uni-koblenz.de wrote:
|  > > Anyone care to make any comments on porting Linux to an SGI Challenge L
|  > > machine w/ (4) R4400 processors?  Am I crazy to even attempt this?
|  >
|  > You're not crazy, after all Linux is already running on bigger iron and
|  > about to run on Sun's E10000.  However you should checkout again what
|  > hardware you actually have on your system.  A Challenge L is mostly like
|  > an Indy (which is supported), that is strictly uniprocessor.  So
|  > your system either is not a multiprocessor system or not a Challenge L.
|  
|  Actually, the Indy system is a Challenge S.  The Indigo^2 system is
|  a Challenge M.   The Challenge L is the desk-side system and can indeed
|  support multiple processors.
|  
|  I can only comment on the model line - not on whether you are crazy or not :)

The hardware is radically different.  The only shared item is the cpu,
and even it's used in a fairly different way.  indy w/o graphics as
challenge S, etc. is strictly a marketing idea.

It's clearly doable, but you need a whole new set of hardware specs.

Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

  reply	other threads:[~1998-12-10 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.981209154550.5530A-100000@mdk187.tucc.uab.edu>
1998-12-10 15:36 ` Linux on an SGI Challenge L ralf
1998-12-10 15:59   ` Steven G. Parker
1998-12-10 16:21     ` Dave Olson [this message]
1998-12-10 16:21       ` Dave Olson
1998-12-10 18:45     ` ralf
1998-12-10 16:08   ` Fernando D. Mato Mira
1998-12-10 16:24   ` Alex deVries
1998-12-10 16:44     ` Dave Olson
1998-12-10 16:44       ` Dave Olson

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=199812101621.IAA84751@anchor.engr.sgi.com \
    --to=olson@anchor.engr.sgi.com \
    --cc=andrewb@uab.edu \
    --cc=linux-smp@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    --cc=sparker@taz.cs.utah.edu \
    /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