public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip question: tulip.o vs de4x5.o
Date: Wed, 24 Nov 2004 08:36:28 +0100	[thread overview]
Message-ID: <20041124073628.GJ2067@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0411231216470.3740@p500>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

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.

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...).

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-24  7:40 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 [this message]
2004-11-24 19:22   ` Jeff Garzik
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=20041124073628.GJ2067@lug-owl.de \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox