Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: "Linux SGI" <linux@cthulhu.engr.sgi.com>
Subject: Re: Nomenclature: "MIPS32", "MIPS64"
Date: Mon, 6 Dec 1999 14:29:06 +0100	[thread overview]
Message-ID: <00a201bf3fed$df8c82f0$0ceca8c0@satanas.mips.com> (raw)

>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.

             reply	other threads:[~1999-12-06 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06 13:29 Kevin D. Kissell [this message]
1999-12-06 13:35 ` Nomenclature: "MIPS32", "MIPS64" Alan Cox
1999-12-06 13:35   ` Alan Cox
1999-12-06 14:19   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
1999-12-06 15:31 Kevin D. Kissell
1999-12-06 15:31 ` Kevin D. Kissell
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='00a201bf3fed$df8c82f0$0ceca8c0@satanas.mips.com' \
    --to=kevink@mips.com \
    --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