Description of problem:
e100 driver doesn't support this devices:
0x1014 0x005c "e100" "IBM|i82557B 10/100"
0x10c3 0x1100 "e100" "Samsung Semiconductors, Inc.|Smartether100 SC1100 LAN
0x1259 0x2560 "e100" "Allied Telesyn International|AT-2560 Fast Ethernet
0x1266 0x0001 "e100" "Microdyne Corporation|NE10/100 Adapter (i82557B)"
0x8086 0x1002 "e100" "Intel Corp.|Pro 100 LAN+Modem 56 Cardbus II"
0x8086 0x1035 "e100" "Intel Corp.|82801CAM (ICH3)/82562EH (LOM) Ethernet
0x8086 0x1036 "e100" "Intel Corp.|82801CAM (ICH3) 82562EH Ethernet Controller"
0x8086 0x1037 "e100" "Intel Corp.|82801CAM (ICH3) Chipset Ethernet Controller"
0x8086 0x1227 "e100" "Intel Corp.|82865 EtherExpress PRO/100A"
0x8086 0x1228 "e100" "Intel Corp.|82556 EtherExpress PRO/100 Smart"
0x8086 0x5200 "e100" "Intel Corp.|EtherExpress PRO/100 Intelligent Server"
0x8086 0x5201 "e100" "Intel Corp.|EtherExpress PRO/100 Intelligent Server"
*** Bug 107597 has been marked as a duplicate of this bug. ***
The intel IDs at least are supported by eepro100; there's no reason that e100
can't support them, I'd think.
e100 _only_ gets support for:
eepro100 , in theory, supports more NIC but _intel guys_ said that it's not
possible because they are special hardware:
and these are strangers for eepro100 and e100 drivers:
Should this be assigned back to me, or is this for hwdata?
it's for hwdata guy(s).
And they need to get a lot of PCI ID's from _all_ net and scsi drivers
because hwdata asignations are very old.
Well, hopefully most new drivers just use their own device tables. In
theory, lots of the pcitable lines can just be removed.
e100 assignations removed in CVS.