Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: SGI joins linux international
Date: Fri, 4 Dec 1998 13:59:06 -0800	[thread overview]
Message-ID: <199812042159.NAA19623@fir.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.96.981204153818.6360A-100000@lager.engsoc.carleton.ca>

Alex deVries writes:
 > 
 > This is obvioulsy very good news; would it be possible for SGI to comment
 > on exactly how they can support us further?
 > 
 > SGI's done a great deal to help us this far, I'm really looking forward t
 > odoing more SGI/Linux stuff.  I see the biggest area where we need help in
 > getting more hardware supported.  That requires getting documentation.  I
 > think it would be great if SGI could allocate someone's time to find said
 > documentation.

       I am working on getting authorization to release more documentation,
as well as fragments of hardware management software and, if possible,
downloadable graphics firmware for those cards which require firmware.
I have agreement in principle, but I need to get agreement on the complete
list of items to be released.

  parent reply	other threads:[~1998-12-04 22:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-04 19:04 SGI joins linux international Ariel Faigon
1998-12-04 19:04 ` Ariel Faigon
1998-12-04 20:42 ` Alex deVries
1998-12-04 21:40   ` Eric Kimminau
1998-12-04 21:59   ` William J. Earl [this message]
1998-12-04 22:30     ` Eric L. Anderson
1998-12-04 22:33       ` William J. Earl
1998-12-06  3:16         ` SGI joins linux internationalt Ken Klingman
1998-12-06  3:16           ` Ken Klingman
1998-12-06  5:36         ` SGI joins linux international ralf

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=199812042159.NAA19623@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --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