All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
Subject: Re: tulip question: tulip.o vs de4x5.o
Date: Wed, 24 Nov 2004 14:22:09 -0500	[thread overview]
Message-ID: <41A4DF61.8050008@pobox.com> (raw)
In-Reply-To: <20041124073628.GJ2067@lug-owl.de>

Jan-Benedict Glaw wrote:
> On Tue, 2004-11-23 12:28:54 -0500, Justin Piszcz <jpiszcz@lucidpixels.com>
> wrote in message <Pine.LNX.4.61.0411231216470.3740@p500>:
> 
>>Each driver works, I have not benchmarked performance with one over the 
>>other with ttcp yet; however, does anyone have any experience with using 
>>one over the other? I see the tulip has several options and the de4x5 
>>seems to be a rather generic driver.
> 
> 
> The de4x5 driver supports some older revisions of the tulip chipset
> which aren't supported by the tulip driver. I guess it could be made to
> support those, too, but nobody did that up to now.

Incorrect, the older chips are supported by the de2104x driver.

de4x5 will be going away.


> You can actually see the difference on older Alphas: de4x5 works while
> tulip doesn't transmit or receive a single packet (getting netdev
> watchdogs later on...).

That's a bug in tulip.

	Jeff




  reply	other threads:[~2004-11-24 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 17:28 tulip question: tulip.o vs de4x5.o Justin Piszcz
2004-11-24  7:36 ` Jan-Benedict Glaw
2004-11-24 19:22   ` Jeff Garzik [this message]
2004-11-24 19:51     ` Justin Piszcz
2004-12-14 10:10     ` Lech Szychowski

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=41A4DF61.8050008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jbglaw@lug-owl.de \
    --cc=jpiszcz@lucidpixels.com \
    --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 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.