public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kwijibo@zianet.com
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3com 3c996b-t support?
Date: Wed, 24 Jul 2002 11:32:33 -0600	[thread overview]
Message-ID: <3D3EE4B1.3000809@zianet.com> (raw)
In-Reply-To: Pine.LNX.4.33.0207241314550.30282-100000@coffee.psychology.mcmaster.ca

It is just that I was reading this page where they evaluate
gigi cards and they used the drivers from 3com.

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

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

Steve

Mark Hahn wrote:

>>drivers out and found out which performs better?  Should I
>>stick with what 3com provides or go with what is in the kernel
>>if it works?
>>    
>>
>
>several good kernel hackers maintain, tune and polish the kernel versions.
>I wouldn't even consider the stuff from the vendor.
>
>
>
>  
>




       reply	other threads:[~2002-07-24 17:20 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 ` kwijibo [this message]
2002-07-24 17:42   ` 3com 3c996b-t support? Jes Sorensen
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=3D3EE4B1.3000809@zianet.com \
    --to=kwijibo@zianet.com \
    --cc=hahn@physics.mcmaster.ca \
    --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