netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
	jgarzik@pobox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, saw@saw.sw.com.sg,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [2.6 patch] the overdue eepro100 removal
Date: Mon, 09 Jul 2007 15:38:27 -0400	[thread overview]
Message-ID: <46928EB3.9020506@tmr.com> (raw)
In-Reply-To: <20070709175251.GG3492@stusta.de>

Adrian Bunk wrote:
> On Mon, Jul 09, 2007 at 01:27:55PM -0400, Bill Davidsen wrote:

> For how many years do you know that there's a new and actively 
> maintained e100 driver for your hardware?
> 
> And if you don't follow a stable line like the 2.6.16 kernel or a 
> distribution kernel it's simply a part of the current development model 
> that some kernel parts change. If changing one driver results in a big 
> problem in your setup you should reconsider your setup. And every new 
> kernel except for -stable kernels will anyway require a revalidation, so 
> changing the network driver as part of this shouldn't be a big issue.
> 
Nothing is a "big issue" if you can force someone else to do the work. 
And if you have no impact from a production outage if some new driver 
works for hours and then does something unexpected.

>>> Why didn't _you_ try the e100 driver when you validated your systems after 
>>> you upgraded them to kernel 2.6, and if you did and it didn't work, where 
>>> is your bug report?
>>>   
>> Is that a joke, or subtle irony? Do you generally validate drivers you 
>> don't use just because your hardware might be able to support them? I don't 
>> validate various accelerated video drivers on systems running mostly text 
>> console, never check sound options on systems with an audio application, 
>> etc. After I tried the e100 driver on the first few systems and found 
>> issues (which may be resolved by now) I went back to eepro100 and used what 
>> worked. And used the driver for any new systems in other installs.
> 
> And exactly this is the reason why the eepro100 driver has to be 
> removed, and that this will result in a better hardware support for 
> everyone in the long term.
> 

If this was a case of a kernel change requiring an effort to keep the 
driver I would not be suggesting someone take time to update the driver 
from threads to tasklets or fartlets or whatever the next ultimate irq 
handling happens to be. But when there's zero effort at the moment to 
retain the driver, I think it's change for the sake of change.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  reply	other threads:[~2007-07-09 20:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 20:21 [2.6 patch] the overdue eepro100 removal Adrian Bunk
2007-07-01 20:33 ` Kok, Auke
2007-07-01 21:51   ` Jeff Garzik
2007-07-02 19:02 ` Bill Davidsen
2007-07-02 21:45   ` Kok, Auke
2007-07-05 16:01     ` Bill Davidsen
2007-07-09 12:52       ` Adrian Bunk
2007-07-09 17:27         ` Bill Davidsen
2007-07-09 17:37           ` Kok, Auke
2007-07-09 17:53             ` Jeff Garzik
2007-07-09 17:52           ` Adrian Bunk
2007-07-09 19:38             ` Bill Davidsen [this message]
2007-07-09 20:43           ` Ian McDonald
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 21:53 Adrian Bunk
2008-08-06 21:10 Adrian Bunk

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=46928EB3.9020506@tmr.com \
    --to=davidsen@tmr.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --cc=torvalds@linux-foundation.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).