Messages in this thread | ![/](/images/icornerl.gif) | | Date | Fri, 14 Feb 2003 19:05:38 +0300 | From | Ivan Kokshaysky <> | Subject | Re: [PATCH] EISA/sysfs update |
| |
On Fri, Feb 14, 2003 at 04:32:50PM +0100, Marc Zyngier wrote: > Ivan> I believe this driver will work for any PCI/EISA bridge without > Ivan> any changes, not only for i82375. Probably we need to look for a > Ivan> class code rather than a device id. > > Unfortunately, the i82375 appears to be unclassified : > > 00:07.0 Non-VGA unclassified device: Intel Corp. 82375EB (rev 03)
We have this code in arch/alpha/kernel/pci.c for ages:
... static void __init quirk_eisa_bridge(struct pci_dev *dev) { dev->class = PCI_CLASS_BRIDGE_EISA << 8; } ... struct pci_fixup pcibios_fixups[] __initdata = { { PCI_FIXUP_HEADER, PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82375, quirk_eisa_bridge }, ...
I think it belongs in drivers/pci/quirks.c.
> I'll had PCI_CLASS_BRIDGE_EISA anyway, just in case.
Actually I thought of replacing "i82375" with "pci_eisa" everywhere in your driver and
static struct pci_device_id pci_eisa_pci_tbl[] = { { PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_CLASS_BRIDGE_EISA << 8, 0xffff00, 0 }, { 0, } };
Ivan. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |