From: "William J. Earl" <wje@fir.engr.sgi.com>
To: "Mark A. Zottola" <asnmaz01@asc.edu>
Cc: Alan Hoyt <neuroinc@unidial.com>,
Ariel Faigon <ariel@cthulhu.engr.sgi.com>,
linux@cthulhu.engr.sgi.com
Subject: Re: Port to R3000 Indigo
Date: Tue, 30 Mar 1999 18:33:10 -0800 [thread overview]
Message-ID: <199903310233.SAA17826@fir.engr.sgi.com> (raw)
In-Reply-To: <37017BA5.160B97BD@asc.edu>
Mark A. Zottola writes:
>
> I would like to second Alan's request. Our port of LINUX to the Indigo2 has
> ground to an unceremonious halt for a lack of hardware documentation. I
> understand that there are legal considerations. Would it not be possible to
> release the documentation under some sort of non-disclosure agreement? As
> we are writing code, if we do not :
>
> 1) include specific citations of the documentation within the comments, or
> 2) discuss those hardware matters deemed as proprietary within the comments
>
> then it seems we could be able to satisfy any non-disclosure agreement SGI
> would have while working under the disclosure constraint of the LINUX's
> GPL. It seems there is an eminently workable way around this if reasonable
> people can come together to discuss this reasonably.
...
For serious developers, we can definitely provide the Indy documentation,
which covers quite a bit of Indigo R4000 and Indigo2, although there are
differences in some places, notably due to those machines using an earlier
revision of the I/O controller (HPC). We are still working on getting a
more general policy on release of documentation, including selected bits
of low-level IRIX code (at least where license issues do not arise). The
Indy situation was a special case, done some time ago.
next prev parent reply other threads:[~1999-03-31 2:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-31 0:25 Port to R3000 Indigo Alan Hoyt
1999-03-31 1:34 ` Mark A. Zottola
1999-03-31 2:33 ` William J. Earl [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-26 20:35 Jeremy Parsons
1999-03-26 21:46 ` tom
1999-03-26 22:08 ` Ariel Faigon
1999-03-26 22:21 ` Martin Mielke
1999-03-26 23:15 ` root
1999-03-27 0:39 ` Ariel Faigon
1999-03-27 0:39 ` Ariel Faigon
1999-03-29 23:38 ` Alan Hoyt
1999-03-30 8:53 ` Ariel Faigon
1999-03-30 8:53 ` Ariel Faigon
1999-03-30 15:29 ` Alan Hoyt
1999-03-31 16:18 ` Mike Shaver
1999-03-27 1:45 ` Theodoros Nikitopoulos
1999-03-27 3:46 ` Steve Martin
1999-03-26 22:21 ` Jurgen Kramer
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=199903310233.SAA17826@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=asnmaz01@asc.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=neuroinc@unidial.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