From: Matthew Wilcox <willy@debian.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] [3/3] PCI segment support
Date: Tue, 8 Apr 2003 00:44:11 +0100 [thread overview]
Message-ID: <20030407234411.GT23430@parcelfarce.linux.theplanet.co.uk> (raw)
I'm putting this patch out for comments rather than merging, since I'm
aware that it won't apply to Linus' tree any more.
- Add segment to pci_bus.
- Change the sysfs name of each device to include a 16-bit segment ID.
diff -urpNX dontdiff linux-2.5.66/drivers/pci/probe.c linux-2.5.66-laptop/drivers/pci/probe.c
--- linux-2.5.66/drivers/pci/probe.c 2003-04-04 08:43:01.000000000 -0600
+++ linux-2.5.66-laptop/drivers/pci/probe.c 2003-04-04 14:36:37.000000000 -0600
@@ -510,7 +510,7 @@ pci_scan_device(struct pci_bus *bus, int
pci_name_device(dev);
/* now put in global tree */
- strcpy(dev->dev.bus_id,dev->slot_name);
+ sprintf(dev->dev.bus_id, "%04x:%s", bus->segment, dev->slot_name);
dev->dev.dma_mask = &dev->dma_mask;
return dev;
diff -urpNX dontdiff linux-2.5.66/drivers/pcmcia/cardbus.c linux-2.5.66-laptop/drivers/pcmcia/cardbus.c
--- linux-2.5.66/drivers/pcmcia/cardbus.c 2003-04-04 08:43:59.000000000 -0600
+++ linux-2.5.66-laptop/drivers/pcmcia/cardbus.c 2003-04-04 14:36:36.000000000 -0600
@@ -282,7 +282,8 @@ int cb_alloc(socket_info_t * s)
pci_setup_device(dev);
- strcpy(dev->dev.bus_id, dev->slot_name);
+ sprintf(dev->dev.bus_id, "%04x:%s", bus->segment,
+ dev->slot_name);
/* We need to assign resources for expansion ROM. */
for (r = 0; r < 7; r++) {
diff -urpNX dontdiff linux-2.5.66/include/linux/pci.h linux-2.5.66-laptop/include/linux/pci.h
--- linux-2.5.66/include/linux/pci.h 2003-04-04 08:43:21.000000000 -0600
+++ linux-2.5.66-laptop/include/linux/pci.h 2003-04-04 14:07:34.000000000 -0600
@@ -451,6 +451,7 @@ struct pci_bus {
void *sysdata; /* hook for sys-specific extension */
struct proc_dir_entry *procdir; /* directory entry in /proc/bus/pci */
+ unsigned short segment; /* domain/segment number */
unsigned char number; /* bus number */
unsigned char primary; /* number of primary bridge */
unsigned char secondary; /* number of secondary bridge */
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next reply other threads:[~2003-04-07 23:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 23:44 Matthew Wilcox [this message]
2003-04-08 16:38 ` [PATCH] [3/3] PCI segment support 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
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=20030407234411.GT23430@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--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