From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "David S. Miller" <davem@redhat.com>,
Linus Torvalds <torvalds@osdl.org>,
Paul Mackerras <paulus@samba.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix ppc ioremap prototype
Date: Thu, 04 Sep 2003 12:06:04 +0200 [thread overview]
Message-ID: <1062669964.1780.66.camel@gaston> (raw)
In-Reply-To: <20030904092834.A27774@infradead.org>
On Thu, 2003-09-04 at 10:28, Christoph Hellwig wrote:
> On Thu, Sep 04, 2003 at 01:10:10AM -0700, David S. Miller wrote:
> > What we could do in the interim is create an ioremap_resource()
> > and then move things over gradually.
>
> ioremap_resource() looks like a fine idea. It's cleaner, easily
> emulateable on <= 2.4 and solves the problem this hack wanted to
> work around properly.
>
> This still doesn't make the phys_addr_t a good interims solution,
> though. Just use ioremap_resource from the beginning for those
> drivers that care for the bigger address space on ppc44x.
>
> Paul, what does actually use this higher addresses?
The great thing with ioremap_resource() is that we can make it work
for PCI IO as well as MMIO and slowly get rid of anything tapping
ports without first ioremapp'ing them. That would help some platforms
with bazillons PCI busses as well so in the end, we don't have to
keep the whole PCI IO space of those machines ioremapped all the time,
this is especially useful on 32 bits archs where we can run short on
virtual space easily.
At first, it would just "do nothing" for PCI IO (just return the same
token), and once enough drivers have been ported, the arch can decide
to change the inx/outx implementation to rely on ioremap_resource
doing the actual mapping.
Ben.
next prev parent reply other threads:[~2003-09-04 10:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 20:32 [PATCH] fix ppc ioremap prototype Christoph Hellwig
2003-09-04 0:33 ` Paul Mackerras
2003-09-04 7:13 ` Christoph Hellwig
2003-09-04 7:25 ` David S. Miller
2003-09-04 7:30 ` Russell King
2003-09-04 7:38 ` Christoph Hellwig
2003-09-04 8:09 ` David S. Miller
2003-09-04 8:12 ` Linus Torvalds
2003-09-04 8:10 ` David S. Miller
2003-09-04 8:28 ` Christoph Hellwig
2003-09-04 10:06 ` Benjamin Herrenschmidt [this message]
2003-09-04 11:03 ` Paul Mackerras
2003-09-04 12:21 ` Geert Uytterhoeven
2003-09-04 12:41 ` Paul Mackerras
2003-09-04 12:41 ` David S. Miller
2003-09-04 12:57 ` Geert Uytterhoeven
2003-09-04 15:58 ` Deepak Saxena
2003-09-04 16:15 ` Geert Uytterhoeven
2003-09-04 16:36 ` Jes Sorensen
2003-09-04 23:18 ` Paul Mackerras
2003-09-05 20:56 ` Geert Uytterhoeven
2003-09-04 16:41 ` Linus Torvalds
2003-09-04 16:43 ` David S. Miller
2003-09-04 17:06 ` Linus Torvalds
2003-09-04 17:03 ` David S. Miller
2003-09-04 17:16 ` Linus Torvalds
2003-09-04 17:13 ` Jeff Garzik
2003-09-04 17:24 ` Linus Torvalds
2003-09-05 8:02 ` Eric W. Biederman
2003-09-04 8:22 ` Christoph Hellwig
2003-09-04 9:29 ` Christoph Hellwig
2003-09-04 10:07 ` Benjamin Herrenschmidt
2003-09-04 9:21 ` Paul Mackerras
2003-09-04 9:36 ` David S. Miller
2003-09-04 9:48 ` Russell King
2003-09-04 9:51 ` Christoph Hellwig
2003-09-04 12:38 ` Paul Mackerras
2003-09-04 12:59 ` Paul Mackerras
2003-09-04 13:01 ` David S. Miller
2003-09-04 14:15 ` Matt Porter
2003-09-04 14:12 ` David S. Miller
2003-09-04 13:30 ` Russell King
2003-09-04 15:50 ` Deepak Saxena
2003-09-04 16:09 ` David S. Miller
2003-09-04 10:34 ` Alan Cox
2003-09-04 10:33 ` David S. Miller
2003-09-04 12:42 ` Jeff Garzik
2003-09-04 12:43 ` David S. Miller
2003-09-04 14:36 ` Matt Porter
2003-09-04 14:30 ` David S. Miller
2003-09-04 15:26 ` Matt Porter
2003-09-04 16:03 ` David S. Miller
2003-09-04 15:35 ` Linus Torvalds
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=1062669964.1780.66.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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