From: "Mark Mason" <mason@broadcom.com>
To: "Jim Gifford" <maillist@jg555.com>
Cc: "Scott Ashcroft" <scott.ashcroft@talk21.com>, linux-mips@linux-mips.org
Subject: Re: pci_iomap issues?
Date: Tue, 06 Dec 2005 15:24:49 -0800 [thread overview]
Message-ID: <43961DC1.80405@broadcom.com> (raw)
In-Reply-To: <4394EDC8.9080301@jg555.com>
Hello,
Jim Gifford wrote:
> How many machines are affected by multiple pci busses. I can only
> thing of the Origin systems. Couldn't we get a base iomap.c in and add
> one's specific to the multiple bus machines?
Any system based on BCM1480s could have multiple pci busses (one PCI-X
directly, and additional busses through HT/PCI-X bridges). For the
BCM91480B board, we had to turn on PCI_DOMAINS to get this to work
correctly.
/Mark
next prev parent reply other threads:[~2005-12-06 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 0:23 pci_iomap issues? Scott Ashcroft
2005-12-06 1:47 ` Jim Gifford
2005-12-06 23:24 ` Mark Mason [this message]
2005-12-07 17:45 ` Scott Ashcroft
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 21:49 Marc Karasek
2005-12-07 21:49 ` Marc Karasek
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=43961DC1.80405@broadcom.com \
--to=mason@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.com \
--cc=scott.ashcroft@talk21.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