From: "William J. Earl" <wje@fir.engr.sgi.com>
To: "Greg Chesson" <greg@xtp.engr.sgi.com>
Cc: "David Chatterton" <chatz@omen.melbourne.sgi.com>,
Lige Hensley <ligeh@carpediem.com>,
Chris Carlson <cwcarlson@home.com>,
linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Thu, 4 Dec 1997 09:22:12 -0800 [thread overview]
Message-ID: <199712041722.JAA26372@fir.engr.sgi.com> (raw)
In-Reply-To: <9712040903.ZM8161@xtp.engr.sgi.com>
Greg Chesson writes:
> I've been reading the O2 thread with great interest.
>
> It seems to me that a "vanilla" port of Linux on the O2 is quite feasible.
> Several writers have agreed.
>
> But full support in Linux for extremem platform-dependent multimedia
> hardware is problematic. This has also been mentioned by several writers,
> some of whom developed the OS code. The problems are twofold: it would
> be a non-trivial task even with full documentation to provide complete
> support for O2 hardware since the job would require as much new invention
> as it would require porting, and second- full disclosure
> of the inner workings is viewed as too much of a giveaway to present
> and future competitors.
>
> Makes me wonder whether the Indy port of Linux could be ratcheted into
> a vanilla port for the O2, and then perhaps SGI could produce binary
> loadable drivers for the missing bits.
For IRIX, most of the O2 work was really in areas which, in
linux, would be reasonably general purpose. In particular, being able
to allocate large pages (64 KB tiles on O2) at any time, no matter how
long the system has been running, was a major change, and would be
useful for performance reasons on any system with variable page size,
since it helps ordinary programs with large address spaces on
large-memory systems, as well as supporting the O2 graphics and
digital media. Similarly, having solid time-scheduled realtime
support is broadly useful. For digital media, one needs a reasonably
portable API, and applications on top of it, which supports high
performance. With those facilities in hand, doing the drivers is not
all that difficult. Providing those facilities, however, is a substantial
project, and not especially tied to SGI hardware.
In graphics, if linux winds up with an IRIX-compatible kernel
graphics driver on some SGI boxes, the IRIX Xsgi, libgl.so, and
libGL.so platform-specific binaries could run on linux. Note that
each of our systems comes with a license for the then-current version
of these components, so loading linux does not preclude using the IRIX
components, although, at present, they may not be shipped in a linux
distribution. Since they are only useful on SGI hardware, perhaps SGI
could make arrangements to permit "stable" binaries to be included in
linux distributions for selected platforms.
next prev parent reply other threads:[~1997-12-04 17:23 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
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 [this message]
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=199712041722.JAA26372@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=chatz@omen.melbourne.sgi.com \
--cc=cwcarlson@home.com \
--cc=greg@xtp.engr.sgi.com \
--cc=ligeh@carpediem.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