From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, ak@suse.de
Subject: [PATCH 1/3] x86 PCI domain support: a humble fix
Date: Fri, 2 Dec 2005 20:39:41 -0500 [thread overview]
Message-ID: <20051203013941.GA2663@havoc.gtf.org> (raw)
In-Reply-To: <20051203013904.GA2560@havoc.gtf.org>
commit 6bc310571a421a755822f1e65815399caddcb400
Author: Jeff Garzik <jgarzik@pobox.com>
Date: Fri Dec 2 19:20:52 2005 -0500
[x86, PCI] pass PCI domain number to PCI config read/write hooks
Don't hardcode zero, since modern x86 (with special ACPI sauce)
can support multiple "PCI segments", aka PCI domains.
arch/i386/pci/common.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
6bc310571a421a755822f1e65815399caddcb400
diff --git a/arch/i386/pci/common.c b/arch/i386/pci/common.c
index f6bc48d..6a18a8a 100644
--- a/arch/i386/pci/common.c
+++ b/arch/i386/pci/common.c
@@ -31,12 +31,14 @@ struct pci_raw_ops *raw_pci_ops;
static int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *value)
{
- return raw_pci_ops->read(0, bus->number, devfn, where, size, value);
+ return raw_pci_ops->read(pci_domain_nr(bus), bus->number,
+ devfn, where, size, value);
}
static int pci_write(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 value)
{
- return raw_pci_ops->write(0, bus->number, devfn, where, size, value);
+ return raw_pci_ops->write(pci_domain_nr(bus), bus->number,
+ devfn, where, size, value);
}
struct pci_ops pci_root_ops = {
next prev parent reply other threads:[~2005-12-03 1:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 1:39 [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03 1:39 ` Jeff Garzik [this message]
2005-12-03 1:40 ` [PATCH 2/3] x86 PCI domain support: struct pci_sysdata Jeff Garzik
2005-12-03 1:40 ` [PATCH 3/3] x86 PCI domain support: the meat Jeff Garzik
2005-12-03 1:42 ` [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03 3:15 ` Andi Kleen
2005-12-03 20:11 ` Jeff Garzik
2005-12-03 21:03 ` Greg KH
2005-12-07 0:39 ` Greg KH
2005-12-07 1:32 ` Andi Kleen
2005-12-07 1:41 ` Greg KH
2005-12-07 2:14 ` Jeff Garzik
2005-12-07 2:33 ` Greg KH
2005-12-07 4:12 ` Jeff Garzik
2005-12-07 5:23 ` Greg KH
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=20051203013941.GA2663@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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).