netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Bill Davidsen <davidsen@tmr.com>
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, 9 Jul 2007 14:52:08 +0200	[thread overview]
Message-ID: <20070709125208.GZ3492@stusta.de> (raw)
In-Reply-To: <468D15F4.6020106@tmr.com>

On Thu, Jul 05, 2007 at 12:01:56PM -0400, Bill Davidsen wrote:
> Please do not make unnecessary kernel changes which require changes in our 
> systems.

Welcome to the kernel 2.6 development model.

> Kok, Auke wrote:
>> Bill Davidsen wrote:
>>> Adrian Bunk wrote:
>>>> This patch contains the overdue removal of the eepro100 driver.
>>>>
>>>> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>>>>
>>> The hardware supported by this driver is still in use, thanks. It's 
>>> probably easier to leave the eepro100 driver in than find anyone who 
>>> wants to investigate why the other driver (e100? from memory) doesn't 
>>> work with some cards. As I recall this was suggested over a year ago and 
>>> it was decided to leave it in, all of the reasons for doing so still seem 
>>> valid. There really doesn't seem to be a benefit, it's not like people 
>>> are working night and day to support new cards for this chip.
>>>
>>
>> please see the thread "Re: [PATCH] fix e100 rx path on ARM (was [PATCH] 
>> e100 rx: or s and el bits)" which is discussing a fix for this issue and 
>> currently being worked.
>>
>> eepro100 will *still* be removed once e100 is fixed to support those 
>> devices.
>>
> Frankly I think there are more of us running old cards on PC hardware than 
> people running ARM! And for a number of card for old buses like ISA, EISA, 
> and VESA, the e100 has not worked. These are old PCs converted to routers 
> and firewalls, and for security should not be left without upgrades.

WTF are you talking about?

Both drivers only support PCI cards.

>> Moreover, we now also have a fix for the e100 IPMI issues on some tyan 
>> boards (patch coming this week!). That hopefully solves all e100 issues 
>> that are still open.
>
> If you think the e100 driver fixes your problems use it and be happy. But 
> since you don't have to test system behavior with the new driver, and you 
> won't be called at night or on weekends if it doesn't work, do the rest of 
> the world a favor and stop taking out things we know to work! Leaving in 
> the eepro100 causes no work for you, and even if e100 works perfectly it 
> needs to be validated in any sane network. it still makes work.

The goal is to get e100 better, and removing eepro100 helps with 
reaching this goal.

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?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-07-09 12:51 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 [this message]
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
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=20070709125208.GZ3492@stusta.de \
    --to=bunk@stusta.de \
    --cc=auke-jan.h.kok@intel.com \
    --cc=davidsen@tmr.com \
    --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).