Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Linux SGI" <linux@cthulhu.engr.sgi.com>
Subject: Nomenclature: "MIPS32", "MIPS64"
Date: Mon, 6 Dec 1999 13:44:55 +0100	[thread overview]
Message-ID: <008301bf3fe7$b5fbb330$0ceca8c0@satanas.mips.com> (raw)

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

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06 12:44 Kevin D. Kissell [this message]
1999-12-06 12:59 ` Nomenclature: "MIPS32", "MIPS64" 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

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='008301bf3fe7$b5fbb330$0ceca8c0@satanas.mips.com' \
    --to=kevink@mips.com \
    --cc=linux@cthulhu.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