From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: powerpc: Revise PPC44x MMU code for arch/powerpc
Date: Tue, 01 May 2007 07:20:24 +1000 [thread overview]
Message-ID: <1177968025.14873.377.camel@localhost.localdomain> (raw)
In-Reply-To: <20070430110107.GH23995@crusty.rchland.ibm.com>
On Mon, 2007-04-30 at 06:01 -0500, Josh Boyer wrote:
> On Mon, Apr 30, 2007 at 02:06:25PM +1000, David Gibson wrote:
> > Index: working-2.6/include/asm-powerpc/mmu-44x.h
> > ===================================================================
> > --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> > +++ working-2.6/include/asm-powerpc/mmu-44x.h 2007-04-30 14:05:35.000000000 +1000
>
> <snip>
>
> > +#ifndef __ASSEMBLY__
> > +
> > +typedef unsigned long long phys_addr_t;
> > +
> > +extern phys_addr_t fixup_bigphys_addr(phys_addr_t, phys_addr_t);
>
> This function can likely get removed entirely in arch/powerpc. ioremap can
> already take a 64 bit address and do the correct thing, so I'm not sure it's
> even needed anymore.
Yeah, the bigphys fixup should'nt be necessary now that resources can be
64 bits. There is -one- thing for which that remapping could still
potentially be useful is... the X server. That bloody POS currently
doesn't deal with PCI very well and will do horrible things to your
system if you try to make it grok 64 bits resources (when it's 32 bits
binary). But then, if you want that working, you need both the above
sort of remapping, but you also need to fix /dev/mem to take it into
account (which the current arch/ppc code doesn't do).
Cheers,
Ben.
prev parent reply other threads:[~2007-04-30 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 4:06 powerpc: Revise PPC44x MMU code for arch/powerpc David Gibson
2007-04-30 11:01 ` Josh Boyer
2007-04-30 11:15 ` David Gibson
2007-04-30 21:20 ` Benjamin Herrenschmidt [this message]
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=1177968025.14873.377.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=jwboyer@linux.vnet.ibm.com \
--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).