From: Matt Porter <mporter@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
rmk@arm.linux.org.uk, hch@lst.de, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix ppc ioremap prototype
Date: Thu, 4 Sep 2003 07:15:35 -0700 [thread overview]
Message-ID: <20030904071535.A22822@home.com> (raw)
In-Reply-To: <20030904060139.5ef43d71.davem@redhat.com>; from davem@redhat.com on Thu, Sep 04, 2003 at 06:01:39AM -0700
On Thu, Sep 04, 2003 at 06:01:39AM -0700, David S. Miller wrote:
> On Thu, 4 Sep 2003 22:59:33 +1000 (EST)
> Paul Mackerras <paulus@samba.org> wrote:
>
> > Perhaps the sensible thing is to have a separate resource tree for
> > each PCI domain (actually two trees, for I/O and memory space),
> > and have them contain bus addresses rather than physical addresses.
>
> I disagree, I think the current model where all resources are
> in a global space makes more sense.
The global space method doesn't allow for proper resource management
in systems with a small floating physical address window but a huge
bus address space to be accessed. MPC8245's DAC scheme is a good
example of this as well as numerous Xscale PCI implementations.
Paul's suggestion would allow the removal of lots of ugly hacks.
-Matt
next prev parent reply other threads:[~2003-09-04 14:15 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
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 [this message]
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=20030904071535.A22822@home.com \
--to=mporter@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.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