From: "Kevin D. Kissell" <kevink@mips.com>
To: "Florian Lohoff" <flo@rfc822.org>, "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 13:02:15 +0200 [thread overview]
Message-ID: <00a301bfbf26$363a5c00$0ceca8c0@satanas.mips.com> (raw)
-----Original Message-----
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@cthulhu.engr.sgi.com>; linux-mips@fnet.fr <linux-mips@fnet.fr>;
linux-mips@vger.rutgers.edu <linux-mips@vger.rutgers.edu>
Date: Tuesday, May 16, 2000 12:22 PM
Subject: Re: Indy Documentation
....
>> 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
While MIPS Technologies Inc owns the microprocessor IP of the
old MIPS Computer Systems, as well as much that was developed
while MIPS was part of SGI, it is less than obvious what rights or
responsibilites the new MIPS Technologies has with respect to the
computer systems part of the pre-SGI MIPS business. It is quite
possible that all that stuff stayed with SGI when MIPS Technologies
spun out. I will forward the message to our legal people and see
what they have to say.
__
Kevin D. Kissell
MIPS Technologies European Architecture Lab
kevink@mips.com
Tel. +33.4.78.38.70.67
FAX. +33.4.78.38.70.68
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Florian Lohoff <flo@rfc822.org>, 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 13:02:15 +0200 [thread overview]
Message-ID: <00a301bfbf26$363a5c00$0ceca8c0@satanas.mips.com> (raw)
Message-ID: <20000516110215.rnLaukMxdRYrO1YoxiXuS0nmsybLH-JcyKOSZBatS44@z> (raw)
-----Original Message-----
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@cthulhu.engr.sgi.com>; linux-mips@fnet.fr <linux-mips@fnet.fr>;
linux-mips@vger.rutgers.edu <linux-mips@vger.rutgers.edu>
Date: Tuesday, May 16, 2000 12:22 PM
Subject: Re: Indy Documentation
....
>> 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
While MIPS Technologies Inc owns the microprocessor IP of the
old MIPS Computer Systems, as well as much that was developed
while MIPS was part of SGI, it is less than obvious what rights or
responsibilites the new MIPS Technologies has with respect to the
computer systems part of the pre-SGI MIPS business. It is quite
possible that all that stuff stayed with SGI when MIPS Technologies
spun out. I will forward the message to our legal people and see
what they have to say.
__
Kevin D. Kissell
MIPS Technologies European Architecture Lab
kevink@mips.com
Tel. +33.4.78.38.70.67
FAX. +33.4.78.38.70.68
next reply other threads:[~2000-05-16 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 11:02 Kevin D. Kissell [this message]
2000-05-16 11:02 ` Indy Documentation Kevin D. Kissell
-- strict thread matches above, loose matches on Subject: below --
2000-05-13 13:21 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
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
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='00a301bfbf26$363a5c00$0ceca8c0@satanas.mips.com' \
--to=kevink@mips.com \
--cc=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