From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: PATCH: fix visws pci (visws specific code)
Date: Fri, 18 Jul 2003 15:03:16 +0100 [thread overview]
Message-ID: <200307181403.h6IE3GQ3017646@hraefn.swansea.linux.org.uk> (raw)
(Andrey Panin)
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux-2.6.0-test1/arch/i386/pci/visws.c linux-2.6.0-test1-ac2/arch/i386/pci/visws.c
--- linux-2.6.0-test1/arch/i386/pci/visws.c 2003-07-10 21:12:50.000000000 +0100
+++ linux-2.6.0-test1-ac2/arch/i386/pci/visws.c 2003-07-15 17:23:53.000000000 +0100
@@ -17,7 +17,7 @@
int broken_hp_bios_irq9;
-extern struct pci_ops pci_direct_conf1;
+extern struct pci_raw_ops pci_direct_conf1;
static int pci_visws_enable_irq(struct pci_dev *dev) { return 0; }
@@ -101,8 +101,9 @@
printk(KERN_INFO "PCI: Lithium bridge A bus: %u, "
"bridge B (PIIX4) bus: %u\n", pci_bus1, pci_bus0);
- pci_scan_bus(pci_bus0, &pci_direct_conf1, NULL);
- pci_scan_bus(pci_bus1, &pci_direct_conf1, NULL);
+ raw_pci_ops = &pci_direct_conf1;
+ pci_scan_bus(pci_bus0, &pci_root_ops, NULL);
+ pci_scan_bus(pci_bus1, &pci_root_ops, NULL);
pci_fixup_irqs(visws_swizzle, visws_map_irq);
pcibios_resource_survey();
return 0;
reply other threads:[~2003-07-18 13:49 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=200307181403.h6IE3GQ3017646@hraefn.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.