Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Ulf Carlsson <ulfc@calypso.engr.sgi.com>,
	linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Re: Indy Documentation
Date: Tue, 16 May 2000 12:08:30 +0200	[thread overview]
Message-ID: <20000516120830.F2191@paradigm.rfc822.org> (raw)
In-Reply-To: <20000515232358.E1682@uni-koblenz.de>; from ralf@oss.sgi.com on Mon, May 15, 2000 at 11:23:58PM +0200

On Mon, May 15, 2000 at 11:23:58PM +0200, Ralf Baechle wrote:
> On Sun, May 14, 2000 at 08:58:18PM +0200, Geert Uytterhoeven wrote:
> 
> > YES! Time to put _all_ docs you can find on CDR. I always keep all technical
> > docs I download to store them on CDR from time to time, since those docs tend
> > to vanish after a while (especially if they were on the manufacturer's
> > website).
> 
> More documentation jewels - I've got now paper copies of R8000 documentation
> and a collection of stuff regarding the R6000.  I was told that the R6000
> was so buggy that understanding the internal circuitry is a prerequisite
> for writing an OS bug now I got everything we need.  Except a R6000
> machine :-)

What is the license or publishing restrictions of those documents ?

> Also I found that there is still a huge pile of Exabyte tapes that have the
> final full backup from the day when MIPS Computer Systems, Inc.  was
> shutdown by SGI after MIPS got bought in the early 90's.  That means that
> provided the legal problems involved with publication of such documentation
> get solved we now have everything that is required to support every machine
> ever made by MIPS Computer Systems, Inc.

How will these legal issues be brought on the track ? I think both
companies (SGI + Mips) should have an interest to free up these documents
or at least hand out to some people who sign some kind of NDA.

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-subject-2-change
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."

  reply	other threads:[~2000-05-16 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13 13:21 Indy Documentation Ulf Carlsson
2000-05-13 13:42 ` Guido Guenther
2000-05-14  6:08   ` Florian Lohoff
2000-05-13 16:32 ` Florian Lohoff
2000-05-14 18:58   ` Geert Uytterhoeven
2000-05-15 21:23     ` Ralf Baechle
2000-05-16 10:08       ` Florian Lohoff [this message]
2000-05-16 16:40         ` Ralf Baechle
     [not found]           ` <Pine.GSO.3.96.1000517124358.24276C-100000@delta.ds2.pg.gda.pl>
2000-05-17 16:06             ` Ralf Baechle
2000-05-16 17:17         ` Nancy Bigham
2000-05-17 11:39           ` Florian Lohoff
2000-05-14 22:04   ` Jan-Benedict Glaw
2000-05-13 23:46 ` Alan Cox
2000-05-13 23:46   ` Alan Cox
2000-05-15 18:22 ` Ulf Carlsson
2000-05-15 19:19   ` Guido Guenther
  -- strict thread matches above, loose matches on Subject: below --
2000-05-16 11:02 Kevin D. Kissell
2000-05-16 11:02 ` Kevin D. Kissell

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=20000516120830.F2191@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=ulfc@calypso.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