Alan Cox wrote:
>
> ethX is what most drivers use. It makes sense to me
I don't think there is any consistency to what drivers do now. A
quick grep of /usr/src/linux-2-2.14/drivers/net shows that the
following drivers register the ethernet device name:
3c59x, ac3200, comx-how-comx, dmfe, eepro, epic100, ncr885e,
ne2k-pci, rtl8139, sdla, sis900, sdlamain, tulip, via-rhine,
yellowfin
and the following register some variant of the card or driver name:
3c501, 3c505, 3c507, 3c509, 3c515, 3c523, 82596, ac3200, am79c961a,
com20020, com90io, com90xx, cops, cosa, cs89x0, de600, de620, depca,
dgrs, e2100, eepro100, eexpress, es3210, eth16i, ewrk3, fmv18x,
hostess_sv11, hp-plus, hp, ibmtr, jazzsonic, lance, lne390, ltpc,
ne.c, ne2.c, ne3210, ni5010, ni52, ni65, olympic, pcnet32, sb1000,
sbni, sealevel, seeq8005, sk_g16, sktr, smc-mca, smc-ultra,
smc-ultra32, smc9194, tlan, wavelan, wd
I'm actually not sure what makes sense. Both pieces of information
(what the driver/hardware is, and what the linux device name is) are
useful in different contexts.
Jeff Garzik wrote:
> After I updated 3c575_cb resource stuff, a couple bug reports made
> their way to lkml when I updated 3c575_cb, talking about how their
> hotplug utilities were now reporting "3c575_cb" as the network
> interface instead of "eth0"
This is a different issue. The PCMCIA tools don't parse /proc/ioports
as that information has never been predictable. The issue with the
new 3c575_cb (and tulip_cb) is a limitation of the new PCI hotplug
interface. The PCMCIA stack wants to know the device name(s) for a
new PCMCIA card, so they can pass this information to user space, so
the device can be configured appropriately. The old CardBus hooks had
a mechanism for relaying this information from a CardBus driver to the
PCMCIA stack. The new hot plug interface doesn't provide a channel
for this information. A hack was implemented, that just writes the
name of the driver into the PCMCIA structure that is supposed to
contain the device name. Which doesn't work.
-- Dave Hinds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:30 EST