From: Anton Blanchard <anton@samba.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Matthew Wilcox <willy@debian.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: pci_domain_nr vs. /sys/devices
Date: Tue, 17 Jun 2003 22:49:50 +1000 [thread overview]
Message-ID: <20030617124950.GF8639@krispykreme> (raw)
In-Reply-To: <20030617134156.A2473@jurassic.park.msu.ru>
Hi,
> Err, this definitely breaks X on alpha. On small and mid-range
> machines we always have pci_domain_nr(bus) == bus->number.
> Practically, it's only Marvel where we could overflow an 8-bit
> bus number.
OK.
> How about this instead?
>
> /* Backwards compatibility for first N PCI domains. */
> if (pci_domain_nr(dev->bus) > PCI_PROC_MAX_DOMAIN)
> return 0;
>
> PCI_PROC_MAX_DOMAIN could be defined in asm/pci.h (255 on alpha), default 0.
A runtime test would be useful, at least for ppc64. That would allow our
older machines to work (multiple host bridges without overlapping
buses). What if we had pci_proc_max_domain and arch code could change its
value during pcibios_init?
Anton
next prev parent reply other threads:[~2003-06-17 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:30 pci_domain_nr vs. /sys/devices Benjamin Herrenschmidt
2003-06-11 14:48 ` Matthew Wilcox
2003-06-11 15:06 ` Benjamin Herrenschmidt
2003-06-11 15:12 ` Matthew Wilcox
2003-06-11 15:40 ` Russell King
2003-06-11 16:00 ` Benjamin Herrenschmidt
2003-06-17 4:52 ` Anton Blanchard
2003-06-11 17:03 ` Patrick Mochel
2003-06-17 4:49 ` Anton Blanchard
2003-06-17 9:41 ` Ivan Kokshaysky
2003-06-17 12:49 ` Anton Blanchard [this message]
2003-06-17 13:11 ` Ivan Kokshaysky
2003-06-17 19:42 ` Matthew Wilcox
2003-06-17 21:30 ` Ivan Kokshaysky
2003-06-18 13:02 ` Matthew Wilcox
2003-06-18 13:24 ` Ivan Kokshaysky
2003-06-17 13:55 ` Matthew Wilcox
2003-06-17 16:25 ` Matthew Wilcox
2003-06-17 18:39 ` Olaf Hering
2003-06-11 15:42 ` Russell King
2003-06-12 0:37 ` Anton Blanchard
2003-06-12 13:27 ` 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=20030617124950.GF8639@krispykreme \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.