the planned eepro100 removal
Subsystems (3)
PATCH 1/1 the planned eepro100 removal
This patch contains the planned removal of the eepro100 driver.
---
Documentation/feature-removal-schedule.txt | 7 MAINTAINERS | 5 drivers/net/Kconfig | 14 drivers/net/Makefile | 1 drivers/net/eepro100.c | 2407 --------------------- 5 files changed, 2434 deletions(-)
9b5df3088f5832963885248102856b6cd2883282
Documentation/feature-removal-schedule.txt +0 -7
@@ -137,13 +137,6 @@ Who: Arjan van de Ven --------------------------- -What: eepro100 network driver -When: January 2007 -Why: replaced by the e100 driver -Who: Adrian Bunk <[email protected]> - ---------------------------- - What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports (temporary transition config option provided until then) The transition config option will also be removed at the same time.
MAINTAINERS +0 -5
@@ -1456,11 +1456,6 @@ L: [email protected] W: bluesmoke.sourceforge.net S: Maintained -EEPRO100 NETWORK DRIVER -P: Andrey V. Savochkin -M: [email protected] -S: Maintained - EFS FILESYSTEM W: http://aeschi.ch.eu.org/efs/ S: Orphan
drivers/net/Kconfig +0 -14
@@ -1454,20 +1454,6 @@ config TC35815 depends on NET_PCI && PCI && MIPS select MII -config EEPRO100 - tristate "EtherExpressPro/100 support (eepro100, original Becker driver)" - depends on NET_PCI && PCI - select MII - help - If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) - card, say Y and read the Ethernet-HOWTO, available from - <http://www.tldp.org/docs.html#howto>. - - To compile this driver as a module, choose M here and read - <file:Documentation/networking/net-modules.txt>. The module - will be called eepro100. - - config E100 tristate "Intel(R) PRO/100+ support" depends on NET_PCI && PCI
drivers/net/Makefile +0 -1
@@ -48,7 +48,6 @@ obj-$(CONFIG_VORTEX) += 3c59x.o obj-$(CONFIG_TYPHOON) += typhoon.o obj-$(CONFIG_NE2K_PCI) += ne2k-pci.o 8390.o obj-$(CONFIG_PCNET32) += pcnet32.o -obj-$(CONFIG_EEPRO100) += eepro100.o obj-$(CONFIG_E100) += e100.o obj-$(CONFIG_TLAN) += tlan.o obj-$(CONFIG_EPIC100) += epic100.o
drivers/net/eepro100.c deleted +0 -2407
2,407 lines not on this page · raw message
Quoted 2 lines · Adrian Bunk
This patch contains the planned removal of the eepro100 driver.
Are the e100 people satisfied that e100 now handles all known cases? I remember that there were corner cases e100 didn't handle, have they all been fixed?
Signature · 3 lines
Bill Davidsen <[email protected]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot
Quoted 4 lines · Bill Davidsen
Quoted 2 lines · Adrian Bunk
This patch contains the planned removal of the eepro100 driver.
Are the e100 people satisfied that e100 now handles all known cases? I
Nope. There are still e100 work outstanding that means we cannot kill eepro100.
Jeff
Quoted 8 lines · Jeff Garzik
Quoted 4 lines · Bill Davidsen
Quoted 2 lines · Adrian Bunk
This patch contains the planned removal of the eepro100 driver.
Are the e100 people satisfied that e100 now handles all known cases? I
Nope. There are still e100 work outstanding that means we cannot kill eepro100.
Agreed, there is still a receive unit hang in the last version that I got from David Acker.
Auke
Quoted 5 lines · Auke
Quoted 4 lines · Jeff Garzik
Quoted 3 lines · Bill Davidsen
Quoted 2 lines · Adrian Bunk
This patch contains the planned removal of the eepro100 driver.
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
Are the e100 people satisfied that e100 now handles all known cases? I
Nope. There are still e100 work outstanding that means we cannot kill eepro100.
Agreed, there is still a receive unit hang in the last version that I got from David Acker.
Auke
Yes, I have not had much time to work on it. :-(
In testing, I was also able to get crashes which I believe are from receive skb corruption.
It doesn't ever appear in our normal use testing, just when using pktgen against it while it uses pktgen out. Sadly this has pushed it down the slippery priority slope.
I am sorry if I am holding things up. I will try to put some more time in on this issue as soon as I can.
-Ack