[Adam J. Richter]
> +static struct pci_device_id isicom_pci_tbl[] __initdata = {
> + { VENDOR_ID, 0x2028, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2051, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2052, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2053, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2054, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2055, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2056, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2057, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2058, PCI_ANY_ID, PCI_ANY_ID },
Eh. Once again the numbers are ugly. Unfortunately the ISICom
situation is non-obvious. Multi-Tech is using the same PCI ID (10b5)
as PLX, even though according to pci.ids they have their own (1122).
Furthermore, the driver source does not indicate which of the five
supported models is which. Oh well, maybe this one *isn't* worth
trying to clean up..
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
