From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] provide PCI resources with a parent
Date: Fri, 06 Aug 2004 20:24:51 +0000 [thread overview]
Message-ID: <200408061324.51802.jbarnes@engr.sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
In working on the patch to export PCI ROM space via sysfs, I found that the
sn2 PCI code doesn't assign a parent resource to any of the PCI device
resources as it builds them. This provides a simple fix for that problem.
Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Thanks,
Jesse
[-- Attachment #2: pci-res-parent.patch --]
[-- Type: text/plain, Size: 1143 bytes --]
===== arch/ia64/sn/io/machvec/pci_bus_cvlink.c 1.42 vs edited =====
--- 1.42/arch/ia64/sn/io/machvec/pci_bus_cvlink.c 2004-06-07 08:45:20 -07:00
+++ edited/arch/ia64/sn/io/machvec/pci_bus_cvlink.c 2004-08-06 10:38:58 -07:00
@@ -290,6 +290,7 @@
addr |= __IA64_UNCACHED_OFFSET;
dev->resource[idx].start = addr;
dev->resource[idx].end = addr + size;
+ dev->resource[idx].parent = &ioport_resource;
}
if (dev->resource[idx].flags & IORESOURCE_IO)
@@ -322,6 +323,7 @@
addr |= __IA64_UNCACHED_OFFSET;
dev->resource[idx].start = addr;
dev->resource[idx].end = addr + size;
+ dev->resource[idx].parent = &iomem_resource;
}
if (dev->resource[idx].flags & IORESOURCE_MEM)
@@ -351,6 +353,7 @@
addr |= __IA64_UNCACHED_OFFSET;
dev->resource[PCI_ROM_RESOURCE].start = addr;
dev->resource[PCI_ROM_RESOURCE].end = addr + size;
+ dev->resource[idx].parent = &iomem_resource;
if (dev->resource[PCI_ROM_RESOURCE].flags & IORESOURCE_MEM)
cmd |= PCI_COMMAND_MEMORY;
}
reply other threads:[~2004-08-06 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200408061324.51802.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@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