Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: Re: Nomenclature: "MIPS32", "MIPS64"
Date: Mon, 6 Dec 1999 10:59:28 -0200	[thread overview]
Message-ID: <19991206105928.I765@uni-koblenz.de> (raw)
In-Reply-To: <008301bf3fe7$b5fbb330$0ceca8c0@satanas.mips.com>

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

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06 12:44 Nomenclature: "MIPS32", "MIPS64" Kevin D. Kissell
1999-12-06 12:59 ` Ralf Baechle [this message]
  -- 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=19991206105928.I765@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=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