From: Jeff Garzik <jeff@garzik.org>
To: Felix Marti <felix@chelsio.com>
Cc: linux-kernel@vger.kernel.org, Netdev List <netdev@vger.kernel.org>
Subject: Re: driver support for Chelsio T210 10Gb ethernet in 2.6.x
Date: Fri, 17 Nov 2006 15:31:30 -0500 [thread overview]
Message-ID: <455E1C22.1090108@garzik.org> (raw)
In-Reply-To: <455E1C01.8000603@garzik.org>
Jeff Garzik wrote:
> Felix Marti wrote:
>> Jeff, as indicated by Chris, the driver that is in the kernel is for
>> N110 and N210. So far, we have not received any customer complaints
>> regarding bugs in the driver and thus it has not been updated in a long
>> time. If you feel like there are some missing features/bug fixes, I'd be
>> glad to spend some time on it.
>>
>> However, Chris's initial request is regarding support for T210. As you
>> indicate, the T210 product is a superset of N110/N210 and i.e. supports
>> TOE. Since the T210 board features additional pieces of hardware, these
>> must be initialized (i.e. memory controllers and TCAM) even if the board
>> is to be used as a NIC only. If the kernel developers are okay with
>> these additional initialization procedures we could update the driver to
>> support N as well as T based products, in NIC mode only, of course ;)
>
>
> I'd welcome support for NIC mode, so, sure...
Well, presuming that active maintenance comes along with it...
Jeff
next prev parent reply other threads:[~2006-11-17 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 3:21 driver support for Chelsio T210 10Gb ethernet in 2.6.x Felix Marti
2006-11-17 20:30 ` Jeff Garzik
2006-11-17 20:31 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 21:28 Chris Stromsoe
2006-11-14 21:33 ` Stephen Hemminger
2006-11-14 21:39 ` Chris Stromsoe
2006-11-14 22:57 ` Jeff Garzik
[not found] ` <20061114153725.730fcd6d@freekitty>
[not found] ` <Pine.LNX.4.64.0611141540110.3416@potato.cts.ucla.edu>
2006-11-16 1:03 ` Stephen Hemminger
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=455E1C22.1090108@garzik.org \
--to=jeff@garzik.org \
--cc=felix@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.