From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Dominic Sweetman <dom@algor.co.uk>,
Matthew Dharm <mdharm@momenco.com>,
linux-mips@oss.sgi.com
Subject: Re: MIPS64 status?
Date: Mon, 14 Jan 2002 15:23:55 -0800 [thread overview]
Message-ID: <20020114152355.E29242@dea.linux-mips.net> (raw)
In-Reply-To: <00ee01c19cfa$ab8d3640$0deca8c0@Ulysses>; from kevink@mips.com on Mon, Jan 14, 2002 at 01:54:42PM +0100
On Mon, Jan 14, 2002 at 01:54:42PM +0100, Kevin D. Kissell wrote:
> The official MIPS64[tm] architecture spec from MIPS
> Technologies also provides a bit (Status.PX) which enables
> the 64-bit data path without affecting address generation
> and translation, which removes this quirk. Only the very
> most recent 64-bit cores and CPUs implement it, however.
And Linux doesn't use PX at all.
Ralf
next prev parent reply other threads:[~2002-01-15 0:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 5:13 MIPS64 status? Matthew Dharm
2002-01-14 8:13 ` Jason Gunthorpe
2002-01-14 20:00 ` Matthew Dharm
2002-01-14 20:00 ` Matthew Dharm
2002-01-14 20:42 ` Jason Gunthorpe
2002-01-14 23:07 ` Ralf Baechle
2002-01-15 0:08 ` Jason Gunthorpe
2002-01-15 20:59 ` Ralf Baechle
2002-01-15 20:00 ` John Heil
2002-01-15 20:55 ` Ralf Baechle
2002-01-16 18:55 ` Dominic Sweetman
2002-01-14 21:17 ` Dominic Sweetman
2002-01-14 21:17 ` Dominic Sweetman
2002-01-14 23:09 ` Ralf Baechle
2002-01-14 11:17 ` Dominic Sweetman
2002-01-14 12:54 ` Kevin D. Kissell
2002-01-14 12:54 ` Kevin D. Kissell
2002-01-14 13:37 ` Maciej W. Rozycki
2002-01-14 23:23 ` Ralf Baechle [this message]
2002-01-15 13:07 ` Maciej W. Rozycki
2002-01-14 23:22 ` Ralf Baechle
2002-01-15 19:11 ` Thiemo Seufer
2002-01-14 23:05 ` Ralf Baechle
2002-01-14 23:25 ` Matthew Dharm
2002-01-14 23:25 ` Matthew Dharm
2002-01-14 23:45 ` Ralf Baechle
2002-01-14 23:59 ` Jason Gunthorpe
2002-01-15 0:27 ` Matthew Dharm
2002-01-15 0:27 ` Matthew Dharm
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=20020114152355.E29242@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=dom@algor.co.uk \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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