Please do not make unnecessary kernel changes which require changes in
our systems.
Kok, Auke wrote:
Bill Davidsen wrote:
Adrian Bunk wrote:
This patch contains the overdue removal of the eepro100 driver.
Signed-off-by: Adrian Bunk <[email protected]>
The hardware supported by this driver is still in use, thanks. It's
probably easier to leave the eepro100 driver in than find anyone who
wants to investigate why the other driver (e100? from memory) doesn't
work with some cards. As I recall this was suggested over a year ago
and it was decided to leave it in, all of the reasons for doing so
still seem valid. There really doesn't seem to be a benefit, it's not
like people are working night and day to support new cards for this
chip.
please see the thread "Re: [PATCH] fix e100 rx path on ARM (was
[PATCH] e100 rx: or s and el bits)" which is discussing a fix for this
issue and currently being worked.
eepro100 will *still* be removed once e100 is fixed to support those
devices.
Frankly I think there are more of us running old cards on PC hardware
than people running ARM! And for a number of card for old buses like
ISA, EISA, and VESA, the e100 has not worked. These are old PCs
converted to routers and firewalls, and for security should not be left
without upgrades.
Moreover, we now also have a fix for the e100 IPMI issues on some tyan
boards (patch coming this week!). That hopefully solves all e100
issues that are still open.
If you think the e100 driver fixes your problems use it and be happy.
But since you don't have to test system behavior with the new driver,
and you won't be called at night or on weekends if it doesn't work, do
the rest of the world a favor and stop taking out things we know to
work! Leaving in the eepro100 causes no work for you, and even if e100
works perfectly it needs to be validated in any sane network. it still
makes work.
--
bill davidsen <[email protected]>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
