From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64
Date: Mon, 14 May 2007 15:50:07 +0200 [thread overview]
Message-ID: <246be0d2277753c0c0b61d0f4131c092@kernel.crashing.org> (raw)
In-Reply-To: <20070514075415.7999BDDEC8@ozlabs.org>
> - Cleanup and separate tracking of the ISA space in the reserved
> low 64K of IO space. No ISA -> Nothing mapped there.
> I now always reserve the first 64K of IO space for the bridge with
> the ISA bus on it.
This is wrong -- there are systems with ISA that
also have PCI devices that require 16-bit legacy
I/O windows (e.g., systems with the AMD8111 chip,
like Maple).
Or do you mean you reserve the low 64k for the PHB?
That would work in this case, but still not in
general. Not sure if we care though.
Segher
next prev parent reply other threads:[~2007-05-14 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 7:53 [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64 Benjamin Herrenschmidt
2007-05-14 7:59 ` Benjamin Herrenschmidt
2007-05-14 8:03 ` Benjamin Herrenschmidt
2007-05-14 9:18 ` Benjamin Herrenschmidt
2007-05-14 13:50 ` Segher Boessenkool [this message]
2007-05-14 20:53 ` Benjamin Herrenschmidt
2007-05-15 0:17 ` Paul Mackerras
2007-05-15 4:33 ` Segher Boessenkool
2007-05-15 6:04 ` Benjamin Herrenschmidt
2007-05-14 14:37 ` Arnd Bergmann
2007-05-14 15:04 ` Segher Boessenkool
2007-05-14 23:56 ` Arnd Bergmann
2007-05-15 0:05 ` Olof Johansson
2007-05-14 20:59 ` Benjamin Herrenschmidt
2007-05-14 23:39 ` Arnd Bergmann
2007-05-15 0:06 ` Benjamin Herrenschmidt
2007-05-15 10:56 ` Christoph Hellwig
2007-05-15 20:42 ` Benjamin Herrenschmidt
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=246be0d2277753c0c0b61d0f4131c092@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--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).