Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: jwiede@blammo.engr.sgi.com (John Wiederhirn)
To: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 2 Dec 1997 16:46:12 -0800	[thread overview]
Message-ID: <9712021646.ZM11626@blammo.engr.sgi.com> (raw)
In-Reply-To: alan@lxorguk.ukuu.org.uk (Alan Cox) "Re: Linux on the O2" (Dec  3, 12:04am)

On Dec 3, 12:04am, Alan Cox wrote:
>
> > I'll second Ralf.  Once we have an Indy port that's stable,
> > easy to install and maybe supported by Red-Hat or other
> > Linux distributors. Once we have something that's actually used
> > by many Indy owners (rather than just a handful), and once SGI
> > real customers (who bring SGI real money) seem to like it and
> > talk to their SGI reps about their interest in Linux on SGI,
> > only then, management may be open to opening more HW specs
> > to the public.
>
> Even if they don't its far far easier to reverse engineer the O2 working
> from a stable Indy base than from a wobbly base platform. I don't personally
> believe there is anything SGI could do to stop a Linux hacker making Linux
> run on the O2

As I've commented before, the problem isn't so much in getting the
kernel working (and working quickly).  The problem comes the second
you need to deal with graphics.  Given the O2's onboard multimedia
hardware, the situation only gets more complex.

Right now, there is no effective hardware abstraction mechanism in
Linux for graphics/multimedia.  With the Indy's rather simple gfx
capabilities, that isn't a tremendous hardship.  The hardship comes
when you are managing things like graphics pipelines, or hardware
that has very specific requirements for memory allocation and
alignment (and access).  Many of the necessary pieces simply do not
currently exist in the Linux kernel services.

While it would be possible to move these needs out to the X server
to some extent, not all of them can be handled that way (in specific,
the memory issues).  Further, there isn't really anything like
uniform functionality in Linux X servers for handling things such
as video I/O, genlocking, etc.  They exist in 3rd party servers,
but then the cooperation requirement rises again.

The proposal has come up multiple times to use the IRIX X server on
top of a Linux kernel.  Unfortunately, once again, that gets very
problemmatic on the more advanced gfx platforms such as O2 and Octane.
They both contain hardware-dependant sections of code which RELY on
certain kernel functionalities being present.  Factor in OpenGL and
the whole complexity level rises again.

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.

My $0.02.


-- 
John Wiederhirn (DSD, Graphics Kernel MTS)        jwiede@engr.sgi.com
    "I've always said there's nothing an agnostic can't do if he
     really doesn't know whether he believes in anything or not."

  reply	other threads:[~1997-12-03  0:48 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 [this message]
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
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=9712021646.ZM11626@blammo.engr.sgi.com \
    --to=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