the scheduled eepro100 removal
Subsystems (3)
PATCH 1/1 the scheduled eepro100 removal
This patch contains the scheduled removal of the eepro100 driver.
---
This patch was already sent on:
- 20 Feb 2007
- 2 Jan 2007
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(-)
Documentation/feature-removal-schedule.txt renamed from Documentation/feature-removal-schedule.txt.old +0 -7
@@ -102,8 +102,1 @@ --------------------------- - -What: eepro100 network driver -When: January 2007 -Why: replaced by the e100 driver -Who: Adrian Bunk <[email protected]> - ----------------------------
MAINTAINERS renamed from MAINTAINERS.old +0 -5
@@ -1077,11 +1077,6 @@ 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 renamed from drivers/net/Kconfig.old +0 -14
@@ -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 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 renamed from drivers/net/Makefile.old +0 -1
@@ -44,7 +44,6 @@ 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 -2406
2,406 lines not on this page · raw message
Quoted 5 lines · Adrian Bunk
This patch contains the scheduled removal of the eepro100 driver.
Signed-off-by Adrian Bunk <[email protected]>
This keeps coming around, but I haven't seen an answer to the questions raised by Eric Piel or Kiszka. I do know that e100 didn't work on some IBM rackmount servers and eepro100 did, but since I'm no longer responsible for those machines I can't retest. Perhaps someone will be able to provide data points.
IBM current offerings as of about three years ago, I had a few dozen of them at one time.
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 9 lines · Bill Davidsen
Quoted 5 lines · Adrian Bunk
This patch contains the scheduled removal of the eepro100 driver.
Signed-off-by Adrian Bunk <[email protected]>This keeps coming around, but I haven't seen an answer to the questions raised by Eric Piel or Kiszka. I do know that e100 didn't work on some IBM rackmount servers and eepro100 did, but since I'm no longer responsible for those machines I can't retest. Perhaps someone will be able to provide data points.
IBM current offerings as of about three years ago, I had a few dozen of them at one time.
We have provided a (test) driver which allows e100 to use IO to communicate with the device, which seems to have helped for one person. I think we need to work with those changes and see if it helps the other people resolve their e100 issues. Unfortunately it keeps slipping off to the low priority list for us.
I suggest that we should push this code into -mm for people to test or something. It's fairly low risk as by default the patch won't enable IO and thus use the old method of writing to the adapter.
Auke
Quoted 7 lines · Auke
Quoted 6 lines · Bill Davidsen
Quoted 5 lines · Adrian Bunk
This patch contains the scheduled removal of the eepro100 driver.
Signed-off-by Adrian Bunk <[email protected]>
Quoted 7 lines
Quoted 3 lines
This keeps coming around, but I haven't seen an answer to the questions raised by Eric Piel or Kiszka. I do know that e100 didn't work on some IBM rackmount servers and eepro100 did, but since I'm no longer responsible for those machines I can't retest. Perhaps someone will be able to provide data points.
IBM current offerings as of about three years ago, I had a few dozen of them at one time.
We have provided a (test) driver which allows e100 to use IO to communicate with the device, which seems to have helped for one person. I think we need to work with those changes and see if it helps the other people resolve their e100 issues. Unfortunately it keeps slipping off to the low priority list for us.
I suggest that we should push this code into -mm for people to test or something. It's fairly low risk as by default the patch won't enable IO and thus use the old method of writing to the adapter.
Sounds sane to me. My overall opinion on eepro100 removal is that we're not there yet. Rare problem cases remain where e100 fails but eepro100 works, and it's older drivers so its low priority for everybody.
Needs to happen, though...
Jeff
Quoted 7 lines · Jeff Garzik
Kok, Auke wrote:
Sounds sane to me. My overall opinion on eepro100 removal is that we're not there yet. Rare problem cases remain where e100 fails but eepro100 works, and it's older drivers so its low priority for everybody.Needs to happen, though...
It seems that several Tyan Opteron base system that were using IPMI add on card. the IPMI card share intel 100Mhz nic onboard. you need to use eepro100 instead of e100 otherwise the e100 will shutdown OOB (out of Band) connection for IPMI when shut down the OS.
YH
Quoted 10 lines
Quoted 5 lines
Sounds sane to me. My overall opinion on eepro100 removal is that we're not there yet. Rare problem cases remain where e100 fails but eepro100 works, and it's older drivers so its low priority for everybody.
Needs to happen, though...
It seems that several Tyan Opteron base system that were using IPMI add on card. the IPMI card share intel 100Mhz nic onboard. you need to use eepro100 instead of e100 otherwise the e100 will shutdown OOB (out of Band) connection for IPMI when shut down the OS.
I find it hard to believe that something as common as IPMI in conjunction with the IPMI technology wasn't tested in Intel's lab. From my experience with Intel Server boards, onboard IPMI (all offered versions) and e100/e1000 NICs, I've never ever experienced any problems operating the BMC over the NIC. Also, I don't quite understand you point about the "IPMI card sharing the 100Mbit/s NIC" onboard? What exactly is shared?
Best regards,
Roberto Nibali, ratz
Signature · 1 line
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
Quoted 12 lines · Roberto Nibali
Quoted 11 lines
Quoted 6 lines
Sounds sane to me. My overall opinion on eepro100 removal is that we're not there yet. Rare problem cases remain where e100 fails but eepro100 works, and it's older drivers so its low priority for everybody.
Needs to happen, though...
It seems that several Tyan Opteron base system that were using IPMI add on card. the IPMI card share intel 100Mhz nic onboard. you need to use eepro100 instead of e100 otherwise the e100 will shutdown OOB (out of Band) connection for IPMI when shut down the OS.
Quoted 7 lines
I find it hard to believe that something as common as IPMI in conjunction with the IPMI technology wasn't tested in Intel's lab. From my experience with Intel Server boards, onboard IPMI (all offered versions) and e100/e1000 NICs, I've never ever experienced any problems operating the BMC over the NIC. Also, I don't quite understand you point about the "IPMI card sharing the 100Mbit/s NIC" onboard? What exactly is shared?
It's a legit problem, but only with this *one* system.
Quoted 23 lines · Jesse
Quoted 12 lines · Roberto Nibali
Quoted 5 lines
Quoted 5 lines
Sounds sane to me. My overall opinion on eepro100 removal is that we're not there yet. Rare problem cases remain where e100 fails but eepro100 works, and it's older drivers so its low priority for everybody.
Quoted 7 lines
Quoted 2 lines
Needs to happen, though...
It seems that several Tyan Opteron base system that were using IPMI add on card. the IPMI card share intel 100Mhz nic onboard. you need to use eepro100 instead of e100 otherwise the e100 will shutdown OOB (out of Band) connection for IPMI when shut down the OS.
Quoted 8 lines
I find it hard to believe that something as common as IPMI in conjunction with the IPMI technology wasn't tested in Intel's lab. From my experience with Intel Server boards, onboard IPMI (all offered versions) and e100/e1000 NICs, I've never ever experienced any problems operating the BMC over the NIC. Also, I don't quite understand you point about the "IPMI card sharing the 100Mbit/s NIC" onboard? What exactly is shared?
Quoted 3 lines
It's a legit problem, but only with this *one* system.
Of course the eepro100 driver is not taking a lot of maintenance either, removing it is not critical as long as there is a legitimate need to support old hardware.
Signature · 3 lines
bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979