From: Ben Greear <greearb@candelatech.com>
To: Ken Brownfield <brownfld@irridia.com>
Cc: Florin Andrei <florin@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.19: eepro100 and cmd_wait issues
Date: Tue, 12 Jun 2001 17:51:08 -0700 [thread overview]
Message-ID: <3B26B8FC.106FBA53@candelatech.com> (raw)
In-Reply-To: <200106121921.OAA05009@asooo.flowerfire.com>
Ken Brownfield wrote:
> OT: does anyone know what the current state of the Tulip driver is and
> if there is good hardware out there? SMC left Tulip and went through at
> least two other chipsets, so the only Tulip card I could find as of a
> couple of years ago was Digital's. But it was astonishingly expensive
> and not clearly supported by the Linux driver.
The current state seems to be 'BUSTED', at least for the cards
that I am trying (ZNYX 4-port, D-LINK 4-port). (I'm using the 2.4
drivers, btw.)
However, I'm hoping that it will be fixed soon, because the D-LINK
4-port is very cheap compared to other 4-ports out there, and in fact
I haven't found a 4-port card that is NOT tulip based (please let
me know if you have 4-port suggestions!)
Other than one really old EEPRO card I have, the EEPRO cards seem to be
very stable, fast, and feature-complete.
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-06-13 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 18:00 2.2.19: eepro100 and cmd_wait issues John Madden
2001-06-12 18:51 ` Florin Andrei
2001-06-12 19:20 ` Ken Brownfield
2001-06-13 0:51 ` Ben Greear [this message]
2001-06-13 0:03 ` David Lang
2001-06-13 1:52 ` Ben Greear
2001-06-13 11:16 ` Henning P. Schmiedehausen
2001-06-14 17:12 ` Florin Andrei
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 21:30 Jason Murphy
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=3B26B8FC.106FBA53@candelatech.com \
--to=greearb@candelatech.com \
--cc=brownfld@irridia.com \
--cc=florin@sgi.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.