netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kosta Todorovic <kostodo@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: jgarzik@pobox.com, tulip-users@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: Network card driver problem (znb.o/tulip)
Date: Fri, 3 Jun 2005 09:58:44 +0400	[thread overview]
Message-ID: <efe3b0060506022258519aa826@mail.gmail.com> (raw)
In-Reply-To: <429FF071.8040707@candelatech.com>

So intel gigE nics use standard tulip linux drivers that come shipped
with a vanilla kernel?

On 6/3/05, Ben Greear <greearb@candelatech.com> wrote:
> Kosta Todorovic wrote:
> > I'm not too concerned with backward compatibility. I see silicom-usa
> > provide both a Broadcom and Intel based chipsets.
> >
> > Is there any reason in particular that you reccomended Broadcom? And
> > can standard kernel drivers be used for these cards? I've had bad
> > expirience with custom manufactorer drivers once they discontinue
> > development and support for their card.
> 
> The BCM NICs will work in a normal 32-bit PCI bus..the 4-port Intels will
> not.  If you have 64-bit PCI-X, then I'd get Intel..but that's just because
> I've used them longer...I have no reason to believe the BCM is inferior at
> this time.
> 
> > How reliable is Silicom-usa?
> >
> > As a management decision, who would you purchase 10 quad port cards
> > from and which kinds of cards would u get?
> 
> Heh, I've already purchased more than 10 from silicom, and have shipped
> them all over the world.  So far...no complaints!  But, if you don't
> need the BCM, you can get good ole Intel quad GigE NICs from www.newegg.com
> and a million other places.
> 
> Ben
> 
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
>

  reply	other threads:[~2005-06-03  5:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  5:51 Network card driver problem (znb.o/tulip) Kosta Todorovic
2005-03-11  6:00 ` Ben Greear
2005-03-11  6:08   ` Kosta Todorovic
2005-03-19  5:33   ` Jon Mason
2005-03-19 10:29     ` Kosta Todorovic
2005-03-19 13:57       ` Jon Mason
2005-03-19 15:23         ` Francois Romieu
2005-03-20 14:05           ` jamal
2005-03-20 19:02             ` Kosta Todorovic
2005-03-20 19:09               ` jamal
2005-03-20 19:18                 ` Kosta Todorovic
2005-03-20 19:29                   ` jamal
2005-03-20 19:36                     ` Kosta Todorovic
2005-03-20 19:38                       ` jamal
2005-03-22  1:59                     ` Jon Mason
2005-03-22  7:18                       ` Kosta Todorovic
2005-03-22 14:56                         ` jamal
2005-05-19  8:02 ` Kosta Todorovic
2005-05-19 17:14   ` Ben Greear
2005-05-20  5:25     ` Kosta Todorovic
2005-05-20 16:07       ` Ben Greear
2005-06-03  5:45         ` Kosta Todorovic
2005-06-03  5:53           ` Ben Greear
2005-06-03  5:58             ` Kosta Todorovic [this message]
2005-06-03  6:25               ` Ben Greear

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=efe3b0060506022258519aa826@mail.gmail.com \
    --to=kostodo@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    --cc=tulip-users@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).