From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Cedric Gavage <cedric.gavage@unixtech.be>,
alan@lxorguk.ukuu.org.uk, netdev@oss.sgi.com
Subject: Re: [Fwd: kernel 2.4.21]
Date: Mon, 28 Jul 2003 11:07:37 -0400 [thread overview]
Message-ID: <20030728150737.GB1399@gtf.org> (raw)
In-Reply-To: <20030728073240.03ff1c2e.davem@redhat.com>
On Mon, Jul 28, 2003 at 07:32:40AM -0700, David S. Miller wrote:
> On Mon, 28 Jul 2003 09:39:11 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
>
> > David S. Miller wrote:
> > > On Wed, 23 Jul 2003 13:40:37 +0200
> > > Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> > >
> > >>Ok, now it's e100 driver, I will wait some hours to see if we have again
> > >>problems, thanks for your help.
> > >
> > > Any problems yet?
> >
> > It's ok now... I was waiting some hours (days) to see if it was really ok ;)
> >
> > Thanks for your help.
>
> No problem.
>
> Alan and Jeff, please note, executive summary:
>
> 1) 'eepro100' driver in 2.4.x + high end EFNET IRC server == crashes
> 2) same as #1 using 'e100' driver == works
My Official Story(tm) is currently
* use e100
* unless you really really want to use eepro100
eepro100 in the kernel tree is essentially unmaintained. One of the
big reasons I merged e100 is that it has an active maintainer with
full access to docs.
Jeff
next prev parent reply other threads:[~2003-07-28 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 17:05 [Fwd: kernel 2.4.21] Alan Cox
2003-07-20 2:17 ` David S. Miller
2003-07-20 8:44 ` Cedric Gavage
2003-07-23 9:23 ` Cedric Gavage
2003-07-23 9:35 ` David S. Miller
2003-07-23 9:44 ` Cedric Gavage
2003-07-23 9:46 ` David S. Miller
2003-07-23 11:30 ` Cedric Gavage
2003-07-23 11:40 ` David S. Miller
2003-07-23 11:40 ` Cedric Gavage
2003-07-27 23:34 ` David S. Miller
2003-07-28 7:39 ` Cedric Gavage
2003-07-28 14:32 ` David S. Miller
2003-07-28 15:07 ` Jeff Garzik [this message]
2003-07-28 15:30 ` Felix Radensky
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=20030728150737.GB1399@gtf.org \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cedric.gavage@unixtech.be \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.