All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: kwijibo@zianet.com
Cc: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: 3com 3c996b-t support?
Date: 24 Jul 2002 13:42:11 -0400	[thread overview]
Message-ID: <m3adohja4s.fsf@trained-monkey.org> (raw)
In-Reply-To: kwijibo@zianet.com's message of "Wed, 24 Jul 2002 11:32:33 -0600"

>>>>> "Steve" == kwijibo  <kwijibo@zianet.com> writes:

Steve> http://www.cs.uni.edu/~gray/gig-over-copper/

Steve> The 3com drivers are open-source though, which makes me less
Steve> hesitent.  And the tigon3 drivers lack of documentation kind of
Steve> irks me.  I would however like to stick with a mainstream
Steve> kernel driver cause the support is there if it is needed.  I
Steve> guess I will give both versions a whirl.  From just glancing at
Steve> the source of both, it seems that both versions support jumbo
Steve> frames which is really what I am after.

Well did you look at the code? It's the infamous Broadcom bcm5700
driver which is probably the worst driver code we have seen in the
Linux community for the last 5 years. Sure you can run it, but don't
come back and complain when you run into trouble. You will be a lot
better off using the tg3 driver, or better yet, getting a NIC thats
less buggy.

Cheers,
Jes

  reply	other threads:[~2002-07-24 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0207241314550.30282-100000@coffee.psychology.mcmaster.ca>
2002-07-24 17:32 ` 3com 3c996b-t support? kwijibo
2002-07-24 17:42   ` Jes Sorensen [this message]
2002-07-24 18:09     ` kwijibo
2002-07-24 18:08       ` Jes Sorensen
2002-07-24 17:12 kwijibo

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=m3adohja4s.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=kwijibo@zianet.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.