public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@evil.netppl.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: 3c590 vs. tulip
Date: Mon, 14 May 2001 13:06:12 +0300	[thread overview]
Message-ID: <20010514130612.A32567@netppl.fi> (raw)
In-Reply-To: <OE73aZbF27y4RbrxUrO000014d0@hotmail.com> <20010511155641.A11827@gruyere.muc.suse.de>
In-Reply-To: <20010511155641.A11827@gruyere.muc.suse.de>

On Fri, May 11, 2001 at 03:56:41PM +0200, Andi Kleen wrote:
> On Fri, May 11, 2001 at 09:27:29AM -0400, Dan Mann wrote:
> > I was just wondering if anybody had an idea which nic card might be a better
> > choice for me; I have a pci 3c590 and a pci smc that uses the tulip driver.
> > I don't have the card number for the smc with me handy, however I know both
> > cards were manufactured in 1995.  Is either card/driver a better choice for
> > a mildly used file server (I am running 2.4.4 Linus)?
> 
> As of 2.4.4 newer 3c90x (I guess you mean that, 3c59x should be mostly
> extinct now) are a better choice because they support zero copy TX and 
> hardware checksumming while tulip does not.
>From what I remember, 3c590 was a horribly buggy card that sometimes
broke even in workstation use (possibly fixed by driver updates more
recently). 3c905B and later are fine, I'm not sure if the original
905 had any bad issues. The original ones definately won't do zero-copy.

The tulips from that era work pretty reliably. Some of the older ones
just won't do autonegotiation (I've seen this with an old 
SMC with both 10/100baseTX and 9-pin "for use with token ring cabling"
connectors). Forcing the link speed works just fine, though.

-- 
Pekka Pietikainen




  parent reply	other threads:[~2001-05-14 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 13:27 3c590 vs. tulip Dan Mann
2001-05-11 13:56 ` Andi Kleen
2001-05-11 14:49   ` Mystery speed: Was " Dan Mann
2001-05-14 10:06   ` Pekka Pietikainen [this message]
2001-05-11 14:23 ` Simon Kirby
  -- strict thread matches above, loose matches on Subject: below --
2001-05-14  8:09 root
2001-05-14  9:46 ` Andi Kleen

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=20010514130612.A32567@netppl.fi \
    --to=pp@evil.netppl.fi \
    --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