From: "William J. Earl" <wje@fir.engr.sgi.com>
To: jwiede@blammo.engr.sgi.com (John Wiederhirn)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 2 Dec 1997 19:06:33 -0800 [thread overview]
Message-ID: <199712030306.TAA05948@fir.engr.sgi.com> (raw)
In-Reply-To: <9712021646.ZM11626@blammo.engr.sgi.com>
John Wiederhirn writes:
...
> Now, having said all that, I do believe the problem is solvable.
> I think that with some modifications of the Linux kernel, it would
> be quite possible to get the necessary abstraction to support
> either an IRIX or customized third-party X server. Further, it
> would be nice if something equivalent to the SGI DMedia libraries
> were available on Linux (with similar hardware abstraction), since
> this is an area where simply put, Linux is FAR behind Windows{95,NT}
> and SGI (and others).
>
> Getting Linux on O2 probably isn't too difficult. Getting USEFUL
> O2/Octane/Onyx2 2D/3D graphics and multimedia under Linux would
> be god-awful difficult with the current kernel/X situation.
...
Having implemented a good bit of the system-specific code for
Indy and O2, I agree entirely. Without the above features, O2 is just
another, not especially distinguished, general purpose workstation,
except for having fairly fast I/O for its price. The most interesting
thing about O2 is what you can do with graphics and multimedia, which
is otherwise possible only with far more expensive hardware. In
different problem domains, something similar can be said of Octane and
the various SGI servers.
WARNING: multiple messages have this Message-ID (diff)
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: John Wiederhirn <jwiede@blammo.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 2 Dec 1997 19:06:33 -0800 [thread overview]
Message-ID: <199712030306.TAA05948@fir.engr.sgi.com> (raw)
Message-ID: <19971203030633.FrHJA0JEGivhg8KajgJdJUkf8NMjyYMvGbcYMty5_10@z> (raw)
In-Reply-To: <9712021646.ZM11626@blammo.engr.sgi.com>
John Wiederhirn writes:
...
> Now, having said all that, I do believe the problem is solvable.
> I think that with some modifications of the Linux kernel, it would
> be quite possible to get the necessary abstraction to support
> either an IRIX or customized third-party X server. Further, it
> would be nice if something equivalent to the SGI DMedia libraries
> were available on Linux (with similar hardware abstraction), since
> this is an area where simply put, Linux is FAR behind Windows{95,NT}
> and SGI (and others).
>
> Getting Linux on O2 probably isn't too difficult. Getting USEFUL
> O2/Octane/Onyx2 2D/3D graphics and multimedia under Linux would
> be god-awful difficult with the current kernel/X situation.
...
Having implemented a good bit of the system-specific code for
Indy and O2, I agree entirely. Without the above features, O2 is just
another, not especially distinguished, general purpose workstation,
except for having fairly fast I/O for its price. The most interesting
thing about O2 is what you can do with graphics and multimedia, which
is otherwise possible only with far more expensive hardware. In
different problem domains, something similar can be said of Octane and
the various SGI servers.
next prev parent reply other threads:[~1997-12-03 3:07 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 [this message]
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
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=199712030306.TAA05948@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=jwiede@blammo.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