LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Bill Davidsen <davidsen@tmr.com>, Adrian Bunk <bunk@stusta.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	saw@saw.sw.com.sg, Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [2.6 patch] the scheduled eepro100 removal
Date: Wed, 28 Mar 2007 18:42:45 -0400	[thread overview]
Message-ID: <460AEF65.8070908@pobox.com> (raw)
In-Reply-To: <460AEB85.1020101@intel.com>

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@stusta.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




  reply	other threads:[~2007-03-28 22:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 14:58 Adrian Bunk
2007-03-28 22:17 ` Bill Davidsen
2007-03-28 22:26   ` Kok, Auke
2007-03-28 22:42     ` Jeff Garzik [this message]
2007-03-29  5:08       ` Yinghai Lu
2007-03-29  8:19         ` Roberto Nibali
2007-03-29 16:22           ` Brandeburg, Jesse
2007-03-30 16:40             ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2007-02-20  0:06 Adrian Bunk
2007-01-02 21:57 Adrian Bunk
2007-01-03  0:07 ` Eric Piel
2007-01-03 22:14   ` Jesse Brandeburg
2007-01-03  9:10 ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460AEF65.8070908@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=davidsen@tmr.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --subject='Re: [2.6 patch] the scheduled eepro100 removal' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).