Re: [2.6 patch] the scheduled eepro100 removal

Previous thread: Re: [PATCH] cpufreq lock rewrite bugfix - Fix locking in cpufreq_get by Venkatesh Pallipadi on Tuesday, January 2, 2007 - 2:27 pm. (1 message)

Next thread: Re: [2.6.19] Scheduler starvation of audio? by Lee Revell on Tuesday, January 2, 2007 - 3:07 pm. (1 message)
From: Adrian Bunk
Date: Tuesday, January 2, 2007 - 2:57 pm

This patch contains the scheduled removal of the eepro100 driver.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 Documentation/feature-removal-schedule.txt |    7 
 MAINTAINERS                                |    5 
 drivers/net/Kconfig                        |   14 
 drivers/net/Makefile                       |    1 
 drivers/net/eepro100.c                     | 2406 ---------------------
 5 files changed, 2433 deletions(-)

--- linux-2.6.20-rc2-mm1/Documentation/feature-removal-schedule.txt.old	2007-01-02 21:28:40.000000000 +0100
+++ linux-2.6.20-rc2-mm1/Documentation/feature-removal-schedule.txt	2007-01-02 21:28:51.000000000 +0100
@@ -102,13 +102,6 @@
 
 ---------------------------
 
-What:   eepro100 network driver
-When:   January 2007
-Why:    replaced by the e100 driver
-Who:    Adrian Bunk <bunk@stusta.de>
-
----------------------------
-
 What:  drivers depending on OSS_OBSOLETE_DRIVER
 When:  options in 2.6.20, code in 2.6.22
 Why:   OSS drivers with ALSA replacements
--- linux-2.6.20-rc2-mm1/MAINTAINERS.old	2007-01-02 21:29:08.000000000 +0100
+++ linux-2.6.20-rc2-mm1/MAINTAINERS	2007-01-02 21:29:14.000000000 +0100
@@ -1077,11 +1077,6 @@
 W:	bluesmoke.sourceforge.net
 S:	Maintained
 
-EEPRO100 NETWORK DRIVER
-P:	Andrey V. Savochkin
-M:	saw@saw.sw.com.sg
-S:	Maintained
-
 EFS FILESYSTEM
 W:	http://aeschi.ch.eu.org/efs/
 S:	Orphan
--- linux-2.6.20-rc2-mm1/drivers/net/Kconfig.old	2007-01-02 21:29:22.000000000 +0100
+++ linux-2.6.20-rc2-mm1/drivers/net/Kconfig	2007-01-02 21:29:38.000000000 +0100
@@ -1471,20 +1471,6 @@
 	  <file:Documentation/networking/net-modules.txt>.  The module
 	  will be called dgrs.
 
-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 ...
From: Eric Piel
Date: Tuesday, January 2, 2007 - 5:07 pm

Hi, I've been using e100 for years with no problem, however more by 
curiosity than necessity I'd like to know how will be handled the 
devices which are (supposedly) supported by eepro100 and not by e100?

According to "modinfo eepro100" and "modinfo e100" those devices IDs are 
only matched by eepro100:
+alias:          pci:v00008086d00001035sv
+alias:          pci:v00008086d00001036sv
+alias:          pci:v00008086d00001037sv
+alias:          pci:v00008086d00001227sv
+alias:          pci:v00008086d00005200sv
+alias:          pci:v00008086d00005201sv

Are they matched by some joker rule that I haven't noticed in e100, or 
is support for them really going to disappear?

See you,
Eric
-

From: Jesse Brandeburg
Date: Wednesday, January 3, 2007 - 3:14 pm

These are phoneline (RJ-11) adapters, I doubt it would work with e100
This was the pro/100 intelligent server adapter with a pro/100 behind
a 960.  There aren't too many of these out there, and they usually
require some special configuration (although they can work as a dumb

I think support for these devices can disappear (as I don't think they
will work anyway) but if someone complains we can take into account
what eepro100 did to support it (if anything) and enable it in e100.

Jesse (e100 maintainer)
-

From: Jan Kiszka
Date: Wednesday, January 3, 2007 - 2:10 am

I'm sorry to disturb the schedule, but I'm not sure right now if this
pending issue of the e100 was meanwhile solved or declared a non-issue:

http://lkml.org/lkml/2006/9/8/105

Auke, can you confirm that it makes sense to re-test? IIRC, our private
thread ended without resolution after I discovered that the chip
revision makes the difference for me. Looked like it is either handled
incorrectly by e100 or screwed up on that board.

Jan
-

Previous thread: Re: [PATCH] cpufreq lock rewrite bugfix - Fix locking in cpufreq_get by Venkatesh Pallipadi on Tuesday, January 2, 2007 - 2:27 pm. (1 message)

Next thread: Re: [2.6.19] Scheduler starvation of audio? by Lee Revell on Tuesday, January 2, 2007 - 3:07 pm. (1 message)