Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Getting X on Linux/SGI
Date: Thu, 19 Jun 1997 13:01:24 -0700	[thread overview]
Message-ID: <199706192001.NAA11640@fir.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.95.970618161248.20293T-100000@lager.engsoc.carleton.ca>

Alex deVries writes:
 > 
 > On Wed, 18 Jun 1997, David S. Miller wrote:
 > 
 > >    From: "John Chen" <chen@betty.esd.sgi.com>
 > >    Date: Wed, 18 Jun 1997 12:41:23 -0700
 > >    I think you also need following stuff for Indy system with Newport graphic:
 > >    1) Newport graphics spec.
 > > I have this.
 > 
 > Q: is the newport graphics spec available outside of SGI?  If so, is there
 > any way for me to get my hands on a copy of it, either electronically or
 > physically?

     With the approval of Tom Furlong (then the SGI VP/GM in charge of Indy),
I provided the specification to the Linux-on-SGI project (in the person
of David Miller :-) ).  It is only available in paper, and David may be
the quickest source for it.  (I am now in a different division, far from
the home of the paper documents.)

  parent reply	other threads:[~1997-06-19 20:01 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199706181641.JAA05598@darwin.esd.sgi.com>
1997-06-18 19:41 ` Getting X on Linux/SGI John Chen
1997-06-18 19:41   ` John Chen
1997-06-18 19:56   ` David S. Miller
1997-06-18 20:15     ` Alex deVries
1997-06-18 21:34       ` http://www.linux.sgi.com? Alex deVries
1997-06-19 20:01       ` William J. Earl [this message]
1997-06-24  0:55 Getting X on Linux/SGI Steve Alexander
  -- strict thread matches above, loose matches on Subject: below --
1997-06-22 17:50 Larry McVoy
1997-06-22 17:50 ` Larry McVoy
1997-06-23 19:43 ` Christopher W. Carlson
1997-06-22 17:36 Larry McVoy
1997-06-20 21:43 Steve Alexander
1997-06-20 21:43 ` Steve Alexander
1997-06-20 16:45 Larry McVoy
1997-06-20 17:06 ` Todd Shrider
1997-06-20 16:40 Larry McVoy
1997-06-20 16:51 ` Mike Shaver
1997-06-20 16:51   ` Mike Shaver
1997-06-20 16:59 ` richard offer
1997-06-20  8:39 Steve Alexander
1997-06-20 15:22 ` Martin Knoblauch
1997-06-20  7:59 Steve Alexander
1997-06-20  7:59 ` Steve Alexander
1997-06-20  8:16 ` David S. Miller
1997-06-20  7:34 Larry McVoy
1997-06-20  9:55 ` William Fisher
1997-06-20  9:17   ` David S. Miller
1997-06-20 10:12     ` Ralf Baechle
1997-06-20 10:12       ` Ralf Baechle
1997-06-20 20:16     ` Nigel Gamble
1997-06-20  9:55   ` William Fisher
1997-06-20 13:42   ` Todd Shrider
1997-06-20 14:07     ` Ralf Baechle
1997-06-20 14:07       ` Ralf Baechle
1997-06-20  7:21 Steve Alexander
     [not found] ` <sca@refugee.engr.sgi.com>
1997-06-20 17:28   ` Christopher W. Carlson
1997-06-23  7:07     ` Martin Knoblauch
1997-06-23 19:31   ` Christopher W. Carlson
1997-06-18 23:16 Larry McVoy
1997-06-18 23:42 ` Nigel Gamble
     [not found]   ` <nigel@cthulhu.engr.sgi.com>
1997-06-19 15:46     ` Christopher W. Carlson
1997-06-19  6:40 ` Ralf Baechle
1997-06-19  6:40   ` Ralf Baechle
1997-06-18  0:00 Good news: no more begging for HW John Wiederhirn
1997-06-18  0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18  0:34   ` Ariel Faigon
1997-06-18 16:28   ` Christopher W. Carlson
1997-06-18 19:30     ` Nigel Gamble

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=199706192001.NAA11640@fir.engr.sgi.com \
    --to=wje@fir.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