linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rupert Eibauer <rupert@ces.ch>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][RFT] Extended BAT features, take 2
Date: Sun, 23 Oct 2005 11:36:51 +0200	[thread overview]
Message-ID: <200510231136.51548.rupert@ces.ch> (raw)
In-Reply-To: <17242.56232.293762.303684@cargo.ozlabs.ibm.com>

On Sunday 23 October 2005 02:39, Paul Mackerras wrote:
> Rupert Eibauer writes:
> 
> > What this patch actually does:
> > - Make CONFIG_PHYS_64BIT selectable for the 6xx family
> 
> Why?  What does this gain us?  

I have I/O resources there which are not reachable in 32 bit mode.

> We still can't use RAM above the 4GB point AFAICS.

Does this mean the page tables do not support 63 bit?

Rupert

  reply	other threads:[~2005-10-23  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 13:54 [PATCH][RFT] Extended BAT features, take 2 Rupert Eibauer
2005-10-23  0:39 ` Paul Mackerras
2005-10-23  9:36   ` Rupert Eibauer [this message]
2005-10-23  9:55     ` Benjamin Herrenschmidt
2005-10-23 11:03       ` Rupert Eibauer
2005-10-23 13:27       ` Rupert Eibauer

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=200510231136.51548.rupert@ces.ch \
    --to=rupert@ces.ch \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).