linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kus Kusche Klaus" <kus@keba.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: My vote against eepro* removal
Date: Thu, 19 Jan 2006 11:08:17 +0100	[thread overview]
Message-ID: <AAD6DA242BC63C488511C611BD51F367323321@MAILIT.keba.co.at> (raw)

> From: Arjan van de Ven
> On Thu, 2006-01-19 at 08:19 +0100, kus Kusche Klaus wrote:
> > Last time I tested (around 2.6.12), eepro100 worked much better 
> > in -rt kernels w.r.t. latencies than e100:
> 
> no offence but this is EXACTLY the reason why having 2 drivers for the
> same hardware is bad. People (in general) will switch to the 
> 2nd driver
> if they hit some thing that is suboptimal, rather than 
> reporting or even
> fixing it. The result of that is that you end up with 2 drivers, each
> serving a portion of the users but both suboptimal in non-overlapping
> ways. Having one driver that's good enough for both groups is clearly
> superior to that....

You describe exactly what happened: I had a problem with e100, I tried
eepro100, I was happy with eepro100 (I didn't notice it was scheduled
for removal), I didn't care about e100 any more...

I also agree that things should not happen that way, but it was the
easy way.

-- 
Klaus Kusche                 (Software Development - Control Systems)
KEBA AG             Gewerbepark Urfahr, A-4041 Linz, Austria (Europe)
Tel: +43 / 732 / 7090-3120                 Fax: +43 / 732 / 7090-6301
E-Mail: kus@keba.com                                WWW: www.keba.com
 

             reply	other threads:[~2006-01-19 10:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 10:08 kus Kusche Klaus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-24  7:38 My vote against eepro* removal kus Kusche Klaus
2006-01-23 11:01 kus Kusche Klaus
2006-01-23 20:23 ` Jesse Brandeburg
2006-01-20 11:27 kus Kusche Klaus
2006-01-20 10:51 kus Kusche Klaus
2006-01-20 11:05 ` Evgeniy Polyakov
2006-01-20 10:19 kus Kusche Klaus
2006-01-20 11:02 ` Evgeniy Polyakov
2006-01-21  0:45 ` Lee Revell
2006-01-20  9:37 kus Kusche Klaus
2006-01-20  9:55 ` Evgeniy Polyakov
2006-01-21  0:40   ` Lee Revell
2006-01-21  1:19     ` John Ronciak
2006-01-21  1:30       ` Lee Revell
2006-01-21  2:01         ` John Ronciak
2006-01-21  3:56           ` Lee Revell
2006-01-19 10:26 kus Kusche Klaus
2006-01-19 16:20 ` Adrian Bunk
2006-01-19 17:16   ` John Ronciak
2006-01-19 19:09 ` Steven Rostedt
2006-01-19 22:57   ` Steven Rostedt
2006-01-19  7:19 kus Kusche Klaus
2006-01-19  7:24 ` Lee Revell
2006-01-19  7:42 ` Arjan van de Ven

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=AAD6DA242BC63C488511C611BD51F367323321@MAILIT.keba.co.at \
    --to=kus@keba.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.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).