netdev - Re: [2.6 patch] the scheduled eepro100 removal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 Mar 2007 18:42:45 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
CC:	Bill Davidsen <davidsen@....com>, Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	saw@....sw.com.sg, Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [2.6 patch] the scheduled eepro100 removal

Kok, Auke wrote:
> Bill Davidsen wrote:
>> Adrian Bunk wrote:
>>> This patch contains the scheduled removal of the eepro100 driver.
>>>
>>> Signed-off-by: Adrian Bunk <bunk@...sta.de>
>>>
>>>
>> 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



-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html