Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Chris Carlson <cwcarlson@home.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 02 Dec 1997 23:46:20 -0800	[thread overview]
Message-ID: <34850E4A.1075E816@home.com> (raw)
In-Reply-To: Pine.LNX.3.95.971202161948.10955B-100000@vertigo.cs.indiana.edu

cypher wrote:

> Hey,
>
> I've been looking for some information to start working on an O2 port and
> have basically gotten the response that managmement at SGI is not willing
> to release hardware specs for the O2 (a mistake IMHO). Don't get me wrong
> I think it's great that they allowed the Indy hardware specs to go out the
> door, even if in a limitied fashion.
>
> (I ran into the same problem with a Nintendo, but don't you agree that the
>  64 would make a great little "Network Computer"?)
>
> I'm guessing that they're looking at this as if an Indy running Linux
> won't really be that competetive with the O2s runnning IRIX, which I can
> almost understand.
>
> I can speak from my personal experience. I working with various research
> and production departments in a university that uses UNIX heavily. I can
> honestly say that we have several platforms (Alpha, Sparc, and Intel) that
> are running linux in production capacity. Also we have a lot of people
> using linux on there workstations (the above platforms plus a slew of
> others).. I think reallity is that people like Linux because they can get
> it to do usefull things on so many platrforms.
>
> Certain organizations within the school, who run anything from O2s to
> Octanes, to a Cave/Reallity Enginge, and an Origin 2000 (ok that
> probably gave away who I was talking about) are considering Linux on
> high-end Intel boxes as a inexpensive replacement for a $6000 dollar O2
> running IRIX. I think this is partly due to the added cost of OS licenses
> and various other software packages they have to pay for. It would be
> ashamed if SGI lost a share of it's hardware sales (even if it is
> the only in workstation market) market becasue some freeware wasn't
> available to run on it.
>
> I realize that SGI has a vested interest in seeing IRIX succeed, and IRIX
> is probably (it hurts to say this) better than Linux when running 128 (or
> soon 4096) CPUs. Linux however, is great lightweight OS for workstations
> especially. There's even more value added to am SGI running Linux that can
> be introduced into an evironment where multiple high-preformance platform
> type are desired (ie, Sparcs, Ultras, Alphas, SGIs. HPs, etc.) but a
> single operating platform is needed.
>
> This makes perfect sense to me, but I don't know if I'm explaining
> everything in the most effecient manner. I'd be _extremely_ happy to
> discuss this with someone, especially people from SGI that have some sort
> of influence on getting us the specs we need.
>
> Right now I am basically in position (not officially supported by the
> university of course, but there not telling me not to do it either, if you
> know what I mean) where I've been given and Indy and an O2 to work on
> porting Linux while on the clock. I don't know how much better it gets,
> but I'm guessing not much... I won't have the hardware forever,
> unfortunately, but if I can start making some sort of progress I can
> possibly convince them of the need to let me keep it.
>
> I hope we can somehow figure out a way for SGI to help us out on this one.
> ;-)
>

I also would like to see Linux ported to the O2 but also don't expect it to
happen in the near future.  We have to remember that SGI is a "hardware
company" and did not get where it is because of software.  To ask them to
divulge the inner workings of their bread-and-butter product, thus allowing
competitors to reproduce and improve upon the design is asking for disaster.
SGI does not fabricate their own chips and they have done their best to
provide access to their source (as long as it doesn't compromise their
hardware investment).  The only thing they have to sell is their design.
Since MIPS is not faring very well against competitors and there seems to me
a bit of doubt that they can stay ahead, what else does SGI have to sell?
Just their internal architecture and IRIX.

Giving the Linux community access to the internal design of the O2, Octane
and/or Origin would give any competitor the information they need to put SGI
out of business.  I don't blame the company for not wanting Linux on the
newer products until the next generation is released.

--
      +----------------------------------------+
      | Christopher W. Carlson                 |
      | e-mail home:      cwcarlson@home.com   |
      | WWW: http://members.home.net/cwcarlson |
      +----------------------------------------+

  parent reply	other threads:[~1997-12-03  6:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-02 21:50 Linux on the O2 cypher
1997-12-02 22:10 ` Ralf Baechle
1997-12-02 22:31   ` Ariel Faigon
1997-12-02 22:31     ` Ariel Faigon
1997-12-03  0:04     ` Alan Cox
1997-12-03  0:46       ` John Wiederhirn
1997-12-03  3:06         ` William J. Earl
1997-12-03  3:06           ` William J. Earl
1997-12-03 18:28         ` cypher
1997-12-03  1:51     ` Douglas F. Elznic
1997-12-03  1:51       ` Douglas F. Elznic
1997-12-03  7:01       ` ralf
     [not found]       ` <Pine.LNX.3.95.971203132942.15095B-100000@vertigo.cs.indian a.edu>
1997-12-03 18:04         ` Douglas F. Elznic
1997-12-03 18:39           ` Alan Cox
1997-12-03 18:39             ` Alan Cox
1997-12-03 18:42           ` cypher
1997-12-03 18:49           ` cypher
1997-12-03 18:05       ` David Chatterton
1997-12-03  2:34         ` Brendan Black
1997-12-03  2:58           ` Richard Offer
1997-12-03  3:19           ` Douglas F. Elznic
1997-12-03  8:21             ` Oliver Frommel
1997-12-03 10:51           ` Alan Cox
1997-12-03 10:51             ` Alan Cox
1997-12-03 18:32           ` cypher
1997-12-03 18:31       ` cypher
1997-12-03 21:19         ` Warner Losh
1997-12-03 22:16           ` Chad Campbell
1997-12-03 22:31             ` William J. Earl
1997-12-03 22:48               ` Alan Cox
1997-12-03 22:48                 ` Alan Cox
     [not found]           ` <Pine.LNX.3.95.971203161250.15277A-100000@dv123s34.lawrence .ks.us>
1997-12-03 22:38             ` Douglas F. Elznic
1997-12-02 22:33   ` William J. Earl
1997-12-02 23:32     ` Christian Reisch
1997-12-02 23:45       ` William J. Earl
1997-12-03  0:09 ` Alan Cox
1997-12-03  0:09   ` Alan Cox
1997-12-03  7:46 ` Chris Carlson [this message]
1997-12-04  5:39   ` Lige Hensley
1997-12-04  5:39     ` Lige Hensley
1997-12-04  5:48     ` David S. Miller
1997-12-04 16:55       ` Greg Chesson
1997-12-04 16:51     ` Greg Chesson
1997-12-04 22:08     ` David Chatterton
1997-12-04 14:06       ` Lige Hensley
1997-12-04 17:03       ` Greg Chesson
1997-12-04 17:22         ` William J. Earl
1997-12-04 18:59           ` Alan Cox
1997-12-04 18:59             ` Alan Cox
1997-12-04 22:01           ` ralf
1997-12-04 23:33             ` William J. Earl
1997-12-05  1:33               ` ralf
1997-12-05  3:25                 ` Chad Campbell
1997-12-04 18:54         ` Alan Cox
1997-12-04 18:54           ` Alan Cox
1997-12-04 19:41           ` Alex deVries
1997-12-04 22:28             ` Eric Kimminau
1997-12-04 22:44               ` Alan Cox
1997-12-05  0:17           ` ralf
1997-12-05  9:06             ` Alan Cox

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=34850E4A.1075E816@home.com \
    --to=cwcarlson@home.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