From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>, "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <ralf@oss.sgi.com>, <linux@cthulhu.engr.sgi.com>
Subject: Re: Nomenclature: "MIPS32", "MIPS64"
Date: Mon, 6 Dec 1999 16:31:13 +0100 [thread overview]
Message-ID: <00b501bf3ffe$f25a9910$0ceca8c0@satanas.mips.com> (raw)
>On Mon, Dec 06, 1999 at 01:35:54PM +0000, Alan Cox wrote:
>
>> I would suggest that until someone from MIPS legal specifically raises an
issue
>> you don't worry about it. With the sparc people they were quite happy with
>> Linux/sparc - which denotes Linux for sparc systems (they objected to
>> sparclinux as that implied it was their product). In fact given the "/" is
>> 'for' then I don't think there is even a valid trademark issue to be raised.
>>
>> Its also not in MIPS interest to cause trouble. Its a product for their
>> system. If they started being silly then everyones lawyers would be advising
>> them to pull their "xyz product for mips" as a legal precaution.
>
>I wouldn't expect MIPS to create any legal problems for anybody; you should
>consider this no more than an advice.
>
> Ralf
Exactly. The point is that there are two different concepts to be represented
in the kernel for which we risk having a name collision, and that the
registration
of the trademark provides an argument somewhat stronger than a coin toss
for resolving it one way and not the other.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Nomenclature: "MIPS32", "MIPS64"
Date: Mon, 6 Dec 1999 16:31:13 +0100 [thread overview]
Message-ID: <00b501bf3ffe$f25a9910$0ceca8c0@satanas.mips.com> (raw)
Message-ID: <19991206153113.8gn4jpBruJkJrrGL8D98Q-lnTz3wqlxb2-t-8q5Qwzc@z> (raw)
>On Mon, Dec 06, 1999 at 01:35:54PM +0000, Alan Cox wrote:
>
>> I would suggest that until someone from MIPS legal specifically raises an
issue
>> you don't worry about it. With the sparc people they were quite happy with
>> Linux/sparc - which denotes Linux for sparc systems (they objected to
>> sparclinux as that implied it was their product). In fact given the "/" is
>> 'for' then I don't think there is even a valid trademark issue to be raised.
>>
>> Its also not in MIPS interest to cause trouble. Its a product for their
>> system. If they started being silly then everyones lawyers would be advising
>> them to pull their "xyz product for mips" as a legal precaution.
>
>I wouldn't expect MIPS to create any legal problems for anybody; you should
>consider this no more than an advice.
>
> Ralf
Exactly. The point is that there are two different concepts to be represented
in the kernel for which we risk having a name collision, and that the
registration
of the trademark provides an argument somewhat stronger than a coin toss
for resolving it one way and not the other.
next reply other threads:[~1999-12-06 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 15:31 Kevin D. Kissell [this message]
1999-12-06 15:31 ` Nomenclature: "MIPS32", "MIPS64" Kevin D. Kissell
-- strict thread matches above, loose matches on Subject: below --
1999-12-06 13:29 Kevin D. Kissell
1999-12-06 13:35 ` Alan Cox
1999-12-06 13:35 ` Alan Cox
1999-12-06 14:19 ` Ralf Baechle
1999-12-06 12:44 Kevin D. Kissell
1999-12-06 12:59 ` Ralf Baechle
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='00b501bf3ffe$f25a9910$0ceca8c0@satanas.mips.com' \
--to=kevink@mips.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@oss.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