From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
Alexandros Kostopoulos <akostop@inaccessnetworks.com>
Subject: Re: pci in arch/powerpc vs arch/ppc
Date: Sat, 11 Aug 2007 18:28:07 -0500 [thread overview]
Message-ID: <1186874887.1576.41.camel@localhost.localdomain> (raw)
In-Reply-To: <2b043cf24b0f5ddda06fcf1f01cb62f3@kernel.crashing.org>
On Thu, 2007-08-09 at 17:56 +0200, Segher Boessenkool wrote:
> > It means the bus on which legacy I/O ports can be found. It's a fairly
> > broken concept; each host bridge should really be treated as a
> > completely separate entity, and if something like a VGA card has legacy
> > I/O ports that need to be used, they should be looked for on the same
> > PCI bus as the card itself. Legacy ISA ports should be discovered
> > through the device tree (or platform devices, or whatever) that
> > explicitly state which PCI-to-ISA bridge they're under.
>
> Currently, Linux does not allow multiple PCI domains to use
> overlapping legacy I/O ranges. Yeah it's a pain.
I have a plan I exposed a little while ago to handle that. We need that
for VGA cards among others anyway.
The idea is basically a call around the lines of
pci_convert_legacy_resource(struct resource *r);
You fill up the resource with flags = MEM/IO and start/end being your
legacy range, and it returns a "fixed" resource that you can use with
inX/outX, or whatever else.
Haven't had time to code something up, and we need to provide a default
impl. for all archs too ... but feel free to volunteer and beat me to
it :-)
Ben.
next prev parent reply other threads:[~2007-08-12 19:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 14:58 pci in arch/powerpc vs arch/ppc Alexandros Kostopoulos
2007-08-03 20:10 ` Scott Wood
2007-08-04 16:39 ` Kumar Gala
2007-08-07 9:06 ` Alexandros Kostopoulos
2007-08-07 15:20 ` Scott Wood
2007-08-08 11:42 ` Alexandros Kostopoulos
2007-08-08 13:03 ` Alexandros Kostopoulos
2007-08-08 16:24 ` Scott Wood
2007-08-08 14:21 ` Alexandros Kostopoulos
2007-08-08 19:11 ` Scott Wood
2007-08-08 19:46 ` Alexandros Kostopoulos
2007-08-08 19:56 ` Scott Wood
2007-08-08 22:20 ` Alexandros Kostopoulos
2007-08-09 15:04 ` Scott Wood
2007-08-09 15:56 ` Segher Boessenkool
2007-08-11 23:28 ` Benjamin Herrenschmidt [this message]
2007-08-10 4:32 ` Paul Mackerras
2007-08-08 22:55 ` Benjamin Herrenschmidt
2007-08-08 16:29 ` MPC8260 PCI9 erratum Scott Wood
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=1186874887.1576.41.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akostop@inaccessnetworks.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).