Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Hartvig Ekner <hartvige@mips.com>
To: sjhill@cotw.com
Cc: hartvige@mips.com (Hartvig Ekner), linux-mips@oss.sgi.com
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?
Date: Tue, 5 Feb 2002 21:53:58 +0100 (MET)	[thread overview]
Message-ID: <200202052053.VAA21843@copsun18.mips.com> (raw)
In-Reply-To: <3C6044A7.13FEB2E2@cotw.com> from "Steven J. Hill" at Feb 05, 2002 02:46:31 PM

Hi,

Steven J. Hill writes:
> 
> Hartvig Ekner wrote:
> > 
> > You have to distinguish between physical and virtual memory. The MIPS32
> > architecture supports implementations with up to 36 bits of physical
> > address space, however the virtual address space in kernel and user mode
> > is as you describe below.
> > 
> I wasn't talking about the MIP32[tm] cores specifically, I was using a
> generalization of 32bit. However, this is good to know. All of the data
> sheets that I just downloaded from the MIPS site for the R4k[X] cores
> don't mention the 36-bit PA item. Care to elaborate?

Sure. All the 4K, 4KE and 4KS families (all MIPS32 cores) from MTI only
provide 32 bits of PA. The 5K and 20K families (MIPS64 implementations)
both provide 36 bit of PA.

Also note that all of the above is only relevant for cores which have a TLB.
The low-end 4K/4KE/4KS cores all come in variants without TLB (to save
die area) and these can of course only generate 32-bits of PA regardless.

/Hartvig

WARNING: multiple messages have this Message-ID (diff)
From: Hartvig Ekner <hartvige@mips.com>
To: sjhill@cotw.com
Cc: Hartvig Ekner <hartvige@mips.com>, linux-mips@oss.sgi.com
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?
Date: Tue, 5 Feb 2002 21:53:58 +0100 (MET)	[thread overview]
Message-ID: <200202052053.VAA21843@copsun18.mips.com> (raw)
Message-ID: <20020205205358.sxMHycGWjtbHhPfFTByX00C43r3lxD4OiMCZAur1MvE@z> (raw)
In-Reply-To: <3C6044A7.13FEB2E2@cotw.com> from "Steven J. Hill" at Feb 05, 2002 02:46:31 PM

Hi,

Steven J. Hill writes:
> 
> Hartvig Ekner wrote:
> > 
> > You have to distinguish between physical and virtual memory. The MIPS32
> > architecture supports implementations with up to 36 bits of physical
> > address space, however the virtual address space in kernel and user mode
> > is as you describe below.
> > 
> I wasn't talking about the MIP32[tm] cores specifically, I was using a
> generalization of 32bit. However, this is good to know. All of the data
> sheets that I just downloaded from the MIPS site for the R4k[X] cores
> don't mention the 36-bit PA item. Care to elaborate?

Sure. All the 4K, 4KE and 4KS families (all MIPS32 cores) from MTI only
provide 32 bits of PA. The 5K and 20K families (MIPS64 implementations)
both provide 36 bit of PA.

Also note that all of the above is only relevant for cores which have a TLB.
The low-end 4K/4KE/4KS cores all come in variants without TLB (to save
die area) and these can of course only generate 32-bits of PA regardless.

/Hartvig

  reply	other threads:[~2002-02-05 20:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 16:50 What is the maximum physical RAM for a 32bit MIPS core? Steven J. Hill
2002-02-05 17:47 ` Hartvig Ekner
2002-02-05 20:46   ` Steven J. Hill
2002-02-05 20:53     ` Hartvig Ekner [this message]
2002-02-05 20:53       ` Hartvig Ekner
2002-02-05 21:15     ` Pete Popov
2002-02-05 21:24       ` Steven J. Hill
2002-02-05 21:44         ` Pete Popov
2002-02-05 21:58         ` Bradley D. LaRonde
2002-02-05 21:58           ` Bradley D. LaRonde
2002-02-06  8:49           ` Geert Uytterhoeven
2002-02-06 11:16             ` nick
2002-02-06 12:07               ` Geert Uytterhoeven
2002-02-06 14:14             ` Bradley D. LaRonde
2002-02-06 14:14               ` Bradley D. LaRonde
2002-02-06  5:29     ` Ralf Baechle
2002-02-06  2:33 ` Ralf Baechle
2002-02-06 13:17   ` William Lee Irwin III

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=200202052053.VAA21843@copsun18.mips.com \
    --to=hartvige@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=sjhill@cotw.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