In 2.5 we should clean up device configuration overall. Make sane the
ether=XXX crap. I do not think modern PCI net drivers need ether=XXX at
all other than for a non-default interface name ("eth4" instead of
"eth0"), for example.
If we decided to handle this on a per-net-driver basis using __setup(),
that would allow us to simply kill the ether=XXX code completely [get it
out of the core rather]. Helper functions called from net driver's
__setup routine would instead be where the common code would exist [in a
smaller form].
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
