| To: | "Kevin D. Kissell" <kevink@mips.com> |
|---|---|
| Subject: | Re: MIPS64 status? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Mon, 14 Jan 2002 15:23:55 -0800 |
| Cc: | Dominic Sweetman <dom@algor.co.uk>, Matthew Dharm <mdharm@momenco.com>, linux-mips@oss.sgi.com |
| In-reply-to: | <00ee01c19cfa$ab8d3640$0deca8c0@Ulysses>; from kevink@mips.com on Mon, Jan 14, 2002 at 01:54:42PM +0100 |
| References: | <20020113211323.A7115@momenco.com> <15426.48692.795968.819750@gladsmuir.algor.co.uk> <00ee01c19cfa$ab8d3640$0deca8c0@Ulysses> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: MIPS64 status?, Ralf Baechle |
|---|---|
| Next by Date: | RE: MIPS64 status?, Matthew Dharm |
| Previous by Thread: | Re: MIPS64 status?, Maciej W. Rozycki |
| Next by Thread: | Re: MIPS64 status?, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |