From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Matthew Wilcox <willy@debian.org>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-kernel@vger.kernel.org, grundler@parisc-linux.org
Subject: Re: [PATCH] [3/3] PCI segment support
Date: Tue, 8 Apr 2003 23:41:13 -0600 [thread overview]
Message-ID: <20030409054113.GA21306@dsl2.external.hp.com> (raw)
In-Reply-To: <20030408173109.GD23430@parcelfarce.linux.theplanet.co.uk>
On Tue, Apr 08, 2003 at 06:31:09PM +0100, Matthew Wilcox wrote:
> On Tue, Apr 08, 2003 at 09:21:19PM +0400, Ivan Kokshaysky wrote:
...
> > I believe each PCI controller on these ia64/parisc boxes has its
> > own config space, and can support up to 256 bridged PCI buses, right?
yes - at least "HP Designed" chipsets do.
> > Whether or not these PCI controllers share the same IO or MEM space is
> > irrelevant (because it's entirely implementation specific).
>
> I think hardware _could_ work like that, but it's never set up to work
> like that in practice.
I interpret "practice" as equivalent to "implementation" in this context.
I hedge by saying "HP designed" because HP tried to sell Intel itanic
boxes until current mckinley boxes became available. And SGI, IBM,
and other vendors are designing their own "high end" ia64 chipsets.
(eg NEC Azusa - 16 CPU itanic).
parisc firmware (both Legacy and PAT PDC) and current IA64 firmware number
the PCI busses. I didn't want the parisc-linux implementation to
reprogram PCI Bus numbers because:
o lack of PCI Segment support (which I'm glad to see willy is fixing)
o the "view" of devices from both firmware and linux should match.
card-mode dino (PCI controller on GSC HBA) is the only exception where
firmware has no clue about the PCI controller.
hth,
grant
next prev parent reply other threads:[~2003-04-09 5:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 23:44 [PATCH] [3/3] PCI segment support Matthew Wilcox
2003-04-08 16:38 ` Ivan Kokshaysky
2003-04-08 16:50 ` Matthew Wilcox
2003-04-08 17:21 ` Ivan Kokshaysky
2003-04-08 17:31 ` Matthew Wilcox
2003-04-09 5:41 ` Grant Grundler [this message]
2003-06-08 16:43 ` Matthew Wilcox
2003-06-08 21:33 ` Russell King
2003-06-08 23:16 ` Alan Cox
2003-06-09 10:07 ` Ivan Kokshaysky
2003-06-09 10:20 ` David S. Miller
2003-06-09 10:42 ` Ivan Kokshaysky
2003-06-09 10:43 ` David S. Miller
2003-06-09 11:00 ` Ivan Kokshaysky
2003-06-09 11:04 ` David S. Miller
2003-06-09 11:17 ` Matthew Wilcox
2003-06-09 11:26 ` Ivan Kokshaysky
2003-06-09 14:34 ` Matthew Wilcox
2003-06-09 11:41 ` Ivan Kokshaysky
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=20030409054113.GA21306@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=grundler@parisc-linux.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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