From: Adrian Cox <adrian@humboldt.co.uk>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org, mj@ucw.cz
Subject: Re: question about PCI setup with multiple CPUs on the PCI bus(es)
Date: Fri, 30 Jan 2004 14:27:10 +0000 [thread overview]
Message-ID: <1075472830.18271.7.camel@newt> (raw)
In-Reply-To: <401941C4.4070502@nortelnetworks.com>
On Thu, 2004-01-29 at 17:24, Chris Friesen wrote:
> Surely we aren't the only people that want to put multiple CPUs on a
> single PCI space. How have people handled this in the past? Ideally
> what I'm looking for is a CONFIG_NO_MANGLE_PCI or something to that
> effect. As a last resort we are considering hardcoding the bus/device
> topology for the two drivers on special daughterboard, but this seems
> really kludgy.
>
> Anyone have any advice?
Having done this a few times before, the basic advice is to design with
a non-transparent bridge, such as an Intel 2155x or a PLX 6254/6540.
That's too late to save you, so you'll need a nasty hack instead.
Faced with your situation, I dealt with it by declaring one processor to
be the root of the PCI bus, and having a task on that processor read the
bus address of each PCI device, and pass those bus addresses to the
processors that needed them. Only the root processor ever made
configuration cycles.
- Adrian Cox
http://www.humboldt.co.uk/
prev parent reply other threads:[~2004-01-30 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 17:24 question about PCI setup with multiple CPUs on the PCI bus(es) Chris Friesen
2004-01-30 14:27 ` Adrian Cox [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=1075472830.18271.7.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
/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