* Nomenclature: "MIPS32", "MIPS64"
@ 1999-12-06 12:44 Kevin D. Kissell
1999-12-06 12:59 ` Ralf Baechle
0 siblings, 1 reply; 8+ messages in thread
From: Kevin D. Kissell @ 1999-12-06 12:44 UTC (permalink / raw)
To: Linux SGI
I note that various people involved in this effort
refer to the 32-bit version of the MIPS/Linux
port as "MIPS32" and the 64-bit version as
"MIPS64". Thus far, I have not observed those
strings making it into the source repositories,
but before they do, there's something I must
point out.
"MIPS32" and "MIPS64" have a very specific
meaning now, and for all I know are already
trademarked/brandmarked/whatever by
MIPS Technologies Inc. to describe the new
baseline ISA and privileged resource architecture
(CP0, in other words) standards for 32-bit
and 64-bit MIPS devices. It's no big deal
for informal discussion, but *please* do not
use the strings "MIPS32" or "MIPS64" in the
code or documentation unless you are really
and truly referring to MIPS32 and MIPS64
as defined by MIPS. If you want to refer to
the 64-bit versus 32-bit Linux ports, please
express it otherwise, e.g. MIPS64bit,
MIPS_64_bit, 64bitMIPS, etc. Otherwise
there is going to be a lot of needless confusion
and a further source schism.
Regards,
Kevin K.
__
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
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: Nomenclature: "MIPS32", "MIPS64"
1999-12-06 12:44 Nomenclature: "MIPS32", "MIPS64" Kevin D. Kissell
@ 1999-12-06 12:59 ` Ralf Baechle
0 siblings, 0 replies; 8+ messages in thread
From: Ralf Baechle @ 1999-12-06 12:59 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: Linux SGI
On Mon, Dec 06, 1999 at 01:44:55PM +0100, Kevin D. Kissell wrote:
> "MIPS32" and "MIPS64" have a very specific
> meaning now, and for all I know are already
> trademarked/brandmarked/whatever by
> MIPS Technologies Inc. to describe the new
> baseline ISA and privileged resource architecture
> (CP0, in other words) standards for 32-bit
> and 64-bit MIPS devices. It's no big deal
> for informal discussion, but *please* do not
> use the strings "MIPS32" or "MIPS64" in the
> code or documentation unless you are really
> and truly referring to MIPS32 and MIPS64
> as defined by MIPS. If you want to refer to
> the 64-bit versus 32-bit Linux ports, please
> express it otherwise, e.g. MIPS64bit,
> MIPS_64_bit, 64bitMIPS, etc. Otherwise
> there is going to be a lot of needless confusion
> and a further source schism.
The use of these terms is pretty coherent with their meaning as given by
Mips, Inc. Linux/MIPS32 is a implementation of Linux (mostly) for MIPS32
processors, Linux/MIPS64 for MIPS64 processors, so I don't see the problem.
Ralf
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
@ 1999-12-06 13:29 Kevin D. Kissell
1999-12-06 13:35 ` Alan Cox
0 siblings, 1 reply; 8+ messages in thread
From: Kevin D. Kissell @ 1999-12-06 13:29 UTC (permalink / raw)
To: Ralf Baechle; +Cc: Linux SGI
>On Mon, Dec 06, 1999 at 01:44:55PM +0100, Kevin D. Kissell wrote:
>
>> "MIPS32" and "MIPS64" have a very specific
>> meaning now, and for all I know are already
>> trademarked/brandmarked/whatever by
>> MIPS Technologies Inc. to describe the new
>> baseline ISA and privileged resource architecture
>> (CP0, in other words) standards for 32-bit
>> and 64-bit MIPS devices. It's no big deal
>> for informal discussion, but *please* do not
>> use the strings "MIPS32" or "MIPS64" in the
>> code or documentation unless you are really
>> and truly referring to MIPS32 and MIPS64
>> as defined by MIPS. If you want to refer to
>> the 64-bit versus 32-bit Linux ports, please
>> express it otherwise, e.g. MIPS64bit,
>> MIPS_64_bit, 64bitMIPS, etc. Otherwise
>> there is going to be a lot of needless confusion
>> and a further source schism.
>
>The use of these terms is pretty coherent with their meaning as given by
>Mips, Inc. Linux/MIPS32 is a implementation of Linux (mostly) for MIPS32
>processors, Linux/MIPS64 for MIPS64 processors, so I don't see the problem.
>
> Ralf
The problems are twofold. First, while it is of course possible to create
a kernel that will run on both MIPS64 and pre-MIPS64 MIPS-III and
MIPS-IV CPUs, it is also possible to create a MIPS64 kernel that
would not necessarily run on R10000s and vice versa. Secondly,
we are referring to two distinct things that ought to be distinguished
at the source and documentation level. We need a name for something
that is 64-bit-MIPS but not necessarily tied up with any particular CPU
and a distinct name for something that is compatible with a particular
CPU type. "MIPS32" and "MIPS64" are already trademarked
by MIPS to describe the CPUs, so we need another name for the
generic OS infrastructure for 64-bit MIPS registers/addresses.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
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
0 siblings, 2 replies; 8+ messages in thread
From: Alan Cox @ 1999-12-06 13:35 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: ralf, linux
> The problems are twofold. First, while it is of course possible to create
> a kernel that will run on both MIPS64 and pre-MIPS64 MIPS-III and
> MIPS-IV CPUs, it is also possible to create a MIPS64 kernel that
> would not necessarily run on R10000s and vice versa. Secondly,
> we are referring to two distinct things that ought to be distinguished
> at the source and documentation level. We need a name for something
> that is 64-bit-MIPS but not necessarily tied up with any particular CPU
> and a distinct name for something that is compatible with a particular
> CPU type. "MIPS32" and "MIPS64" are already trademarked
> by MIPS to describe the CPUs, so we need another name for the
> generic OS infrastructure for 64-bit MIPS registers/addresses.
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
1999-12-06 13:35 ` Alan Cox
@ 1999-12-06 13:35 ` Alan Cox
1999-12-06 14:19 ` Ralf Baechle
1 sibling, 0 replies; 8+ messages in thread
From: Alan Cox @ 1999-12-06 13:35 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: ralf, linux
> The problems are twofold. First, while it is of course possible to create
> a kernel that will run on both MIPS64 and pre-MIPS64 MIPS-III and
> MIPS-IV CPUs, it is also possible to create a MIPS64 kernel that
> would not necessarily run on R10000s and vice versa. Secondly,
> we are referring to two distinct things that ought to be distinguished
> at the source and documentation level. We need a name for something
> that is 64-bit-MIPS but not necessarily tied up with any particular CPU
> and a distinct name for something that is compatible with a particular
> CPU type. "MIPS32" and "MIPS64" are already trademarked
> by MIPS to describe the CPUs, so we need another name for the
> generic OS infrastructure for 64-bit MIPS registers/addresses.
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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
1999-12-06 13:35 ` Alan Cox
1999-12-06 13:35 ` Alan Cox
@ 1999-12-06 14:19 ` Ralf Baechle
1 sibling, 0 replies; 8+ messages in thread
From: Ralf Baechle @ 1999-12-06 14:19 UTC (permalink / raw)
To: Alan Cox; +Cc: Kevin D. Kissell, ralf, linux
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
@ 1999-12-06 15:31 Kevin D. Kissell
1999-12-06 15:31 ` Kevin D. Kissell
0 siblings, 1 reply; 8+ messages in thread
From: Kevin D. Kissell @ 1999-12-06 15:31 UTC (permalink / raw)
To: Ralf Baechle, Alan Cox; +Cc: ralf, linux
>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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Nomenclature: "MIPS32", "MIPS64"
1999-12-06 15:31 Kevin D. Kissell
@ 1999-12-06 15:31 ` Kevin D. Kissell
0 siblings, 0 replies; 8+ messages in thread
From: Kevin D. Kissell @ 1999-12-06 15:31 UTC (permalink / raw)
To: Ralf Baechle, Alan Cox; +Cc: linux
>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.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~1999-12-06 15:31 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-12-06 12:44 Nomenclature: "MIPS32", "MIPS64" Kevin D. Kissell
1999-12-06 12:59 ` Ralf Baechle
-- 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 15:31 Kevin D. Kissell
1999-12-06 15:31 ` Kevin D. Kissell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox