I can find no reason for the _p on the serverworks IRQ routing logic, and
a review of the documentation contains no indication that any such delay
is needed so lets try this
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc6-mm1/arch/x86/pci/irq.c
linux-2.6.24-rc6-mm1/arch/x86/pci/irq.c
--- linux.vanilla-2.6.24-rc6-mm1/arch/x86/pci/irq.c 2008-01-02
16:04:19.000000000 +0000
+++ linux-2.6.24-rc6-mm1/arch/x86/pci/irq.c 2008-01-11 15:21:17.000000000
+0000
@@ -461,14 +461,14 @@
*/
static int pirq_serverworks_get(struct pci_dev *router, struct pci_dev *dev,
int pirq)
{
- outb_p(pirq, 0xc00);
+ outb(pirq, 0xc00);
return inb(0xc01) & 0xf;
}
static int pirq_serverworks_set(struct pci_dev *router, struct pci_dev *dev,
int pirq, int irq)
{
- outb_p(pirq, 0xc00);
- outb_p(irq, 0xc01);
+ outb(pirq, 0xc00);
+ outb(irq, 0xc01);
return 1;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
