Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: cypher <cypher@vertigo.cs.indiana.edu>, linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 2 Dec 1997 14:33:41 -0800	[thread overview]
Message-ID: <199712022233.OAA05434@fir.engr.sgi.com> (raw)
In-Reply-To: <19971202231009.32146@grass.uni-koblenz.de>

Ralf Baechle writes:
 > On Tue, Dec 02, 1997 at 04:50:40PM -0500, cypher wrote:
...
 > Actually aside of the Linux developers like me there are also SGI engineers
 > interested in Linux as well as some ties on this list, so posting here was
 > a right thing to do.

      I am one of the SGI engineers, and I would like to be able to release
the O2 specifications.  Releasing the Indy specifications basically happened
when we had started shipping O2, and the Indy was thus obsolete as a hardware
product.  I expect it would be easy to get approval when O2 is no longer
shipping, but doing it now will take some persuasion.

 > I can well imagine that way can be found under which an O2 port could become
 > reality.  It's probably most important that customers (== $$$) ask for Linux
 > for their boxes and that word has to spread upto the higher managment.

       This is precisely correct.  If enough large customers ask for it,
it will happen.  The problem so far has been persuading management that
very many people would consider SGI boxes with Linux.  Part of the
problem is that a simple Linux port leaves much of the special features
of the SGI system unused, and really exploiting the graphics and digital
media features is a major project, when SGI already has too many projects
underway.  

 > > 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 suggest to work on the Indy.  There is Indy code that just needs a bit of
 > polishing and debugging, but essentially we're relativly close.  Working for
 > the O2 would mean that you'll aside of a bigger technical task you'll also
 > have to solve a political problem.

      O2 is also a bigger technical problem, even with specifications in hand.
The drivers are actually easier than for Indy, but really exploiting the
O2 capabilities in graphics and digital media required a lot of enhancements
to the memory management, since O2 is a UMA system.  You could do a dumb
port, with a fixed frame buffer size, but then most of the O2 is wasted.

  parent reply	other threads:[~1997-12-02 22:35 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 [this message]
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
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=199712022233.OAA05434@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=cypher@vertigo.cs.indiana.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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