From: Francois Romieu <romieu@cogenit.fr>
To: John Jasen <jjasen1@umbc.edu>
Cc: Ken Brownfield <brownfld@irridia.com>, J Sloan <joe@tmsusa.com>,
linux-kernel@vger.kernel.org
Subject: Re: Recommendations about a 100/10 NIC
Date: Wed, 6 Mar 2002 22:42:19 +0100 [thread overview]
Message-ID: <20020306224219.A1046@fafner.intra.cogenit.fr> (raw)
In-Reply-To: <20020306111502.D8107@asooo.flowerfire.com> <Pine.SGI.4.31L.02.0203061234520.6241227-100000@irix2.gl.umbc.edu>
In-Reply-To: <Pine.SGI.4.31L.02.0203061234520.6241227-100000@irix2.gl.umbc.edu>; from jjasen1@umbc.edu on Wed, Mar 06, 2002 at 12:36:24PM -0500
John Jasen <jjasen1@umbc.edu> :
[...]
> My stock recommendation is thus SMC EtherPower II cards.
Not all revisions behave the same here. For a few months, I've seen
3c905{b/c} working fine where etherpower II suffered.
YMMV. A lot.
--
Ueimor
next prev parent reply other threads:[~2002-03-06 21:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 12:18 janvapan
2002-03-03 14:22 ` Justin Piszcz
2002-03-03 20:29 ` Bernd Eckenfels
2002-03-03 21:04 ` Hans-Christian Armingeon
2002-03-04 3:05 ` rddunlap
2002-03-03 21:37 ` Hans-Christian Armingeon
2002-03-03 17:15 ` J Sloan
2002-03-03 20:39 ` LA Walsh @ tlinx.org
2002-03-04 1:04 ` J Sloan
2002-03-07 8:21 ` Kelsey Hudson
2002-03-06 17:15 ` Ken Brownfield
2002-03-06 17:36 ` John Jasen
2002-03-06 17:28 ` Tim Hockin
2002-03-06 18:30 ` Michael Sterrett -Mr. Bones.-
2002-03-06 18:33 ` John Jasen
2002-03-06 21:42 ` Francois Romieu [this message]
2002-03-08 1:47 ` Ken Brownfield
2002-03-07 5:06 ` J Sloan
2002-03-07 8:16 ` Kelsey Hudson
[not found] <Pine.LNX.4.10.10203031559090.801-100000@oakley.chf>
2002-03-03 16:25 ` Justin Piszcz
2002-03-04 5:15 ` Mike Fedyk
2002-03-04 9:54 ` Vojtech Pavlik
[not found] <fa.fifmv4v.ogc1qa@ifi.uio.no>
[not found] ` <fa.jgnh1iv.1ek48ih@ifi.uio.no>
2002-03-04 6:49 ` Dan Maas
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=20020306224219.A1046@fafner.intra.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=brownfld@irridia.com \
--cc=jjasen1@umbc.edu \
--cc=joe@tmsusa.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
all inboxes | Powered by JetHome®