Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: 4819 <rmk@shell.mdc.net>, linux@cthulhu.engr.sgi.com
Subject: Re: sound, power button, volume buttons
Date: Wed, 29 Jul 1998 18:50:07 +0200	[thread overview]
Message-ID: <19980729185007.K771@uni-koblenz.de> (raw)
In-Reply-To: <199807291540.IAA20337@fir.engr.sgi.com>; from William J. Earl on Wed, Jul 29, 1998 at 08:40:10AM -0700

On Wed, Jul 29, 1998 at 08:40:10AM -0700, William J. Earl wrote:

>      I can generally answer specific questions.  Also, I can arrange to send
> a copy of the documentation to people who want to actively work on the
> project.  (The informal limited distribution agreement was the basis on which
> the management agreed to let us release the documentation.)  
> 
>      People have asked about documentation for other products.  In general,
> I don't know where to find documentation for any of the SGI R3000-based systems.

Do you think a ``Call for dusty Paper'' CfdP (TM) on the Usenet in groups
like comp.sys.mips or comp.sys.sgi.* might make sense?  I bet there are
still people out there, maybe former SGI employees in the meantime which
have helpful data around.

> I do have incomplete documentation for some of the MIPS systems.

I'm currently doing some brain surgery on some OEM machine which identifies
itself as RS3230 and is running RISC/os 4.50 :-)

>                                                                   SGI will
> probably be reluctant to release Challenge, Origin, or Octane documentation
> anytime soon, although that might change if we persuade the management to
> embrace linux officially (which might happen if the linux commercial server
> business on other platforms continues to expand rapidly).  I also have
> not found much documentation for Indigo R4000, although it is fairly
> similar to Indy and Indigo2.  Indigo2 is very close to Indy, although
> XZ and better graphics differ from the base XL/Newport graphics on Indy
> and some low-end Indigo2 systems; Indigo2 and Indy run the same IRIX kernel
> binary.  O2 documentation is quite good, and the electronic versions are
> readily available, but I do not have approval to release that documentation
> at present; that might change if we agree to facilitate early linix ports
> to our next generation workstations, and will likely change once O2 goes
> out of production.

As I already wrote to Richard Masoner - it's not uncommon that people
write GPL software while being under NDA.  The company reviews the code
when it is finished and gives it's ok to publish it but the documentation
(whatever it consists of - paper, code, electronic files, drawings ...)
will stay undisclosed.  In many cases this is a way to keep both sides
happy.

Since you mentioned the various graphic subsystems above - do you think
the implementation of a ARC firmware text only based console might be
sensible?  I've got several requests for Linux from people who have a
XZ graphic which we don't support yet - and there is quite a number of
graphic options for SGI's out there so this might be somewhat helpful.

  Ralf

  reply	other threads:[~1998-07-29 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSI.3.96.980729001735.24028A-100000@shell.mdc.net>
     [not found] ` <19980729090902.D1989@uni-koblenz.de>
1998-07-29 15:40   ` sound, power button, volume buttons William J. Earl
1998-07-29 16:50     ` ralf [this message]
1998-07-29 17:31       ` Richard Ingram
1998-07-29 18:19       ` William J. Earl
1998-07-29 22:04       ` Alistair Lambie
1998-07-29 22:37         ` William J. Earl
1998-07-29 23:41         ` 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=19980729185007.K771@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=rmk@shell.mdc.net \
    --cc=wje@fir.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