All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Steven J. Hill" <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: Wed, 6 Feb 2002 06:29:45 +0100	[thread overview]
Message-ID: <20020206062945.A13634@dea.linux-mips.net> (raw)
In-Reply-To: <3C6044A7.13FEB2E2@cotw.com>; from sjhill@cotw.com on Tue, Feb 05, 2002 at 02:46:31PM -0600

On Tue, Feb 05, 2002 at 02:46:31PM -0600, Steven J. Hill wrote:

> > One note: Many MIPS32 implementations choose not to implement all 36 PA
> > bits, but limit themselves to 32 bits. This saves a few bits in the TLB
> > and a few address lines.
> > 
> So, if someone did want 36 PA bits on Linux, the TLB exception handlers
> and a little of the page table construction/management code would have to
> change. The userspace contraints and such would still remain. Cool.

Basically the whole code is already in place except a few bugs fixes that
still need to go in.

  Ralf

  parent reply	other threads:[~2002-02-06 19:18 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
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 [this message]
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=20020206062945.A13634@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.