From: Ben Hutchings <bhutchings@solarflare.com>
To: netdev@vger.kernel.org
Cc: linux-net-drivers@solarflare.com
Subject: [PATCH] [RFC] New driver "sfc" for Solarstorm SFC4000 controller
Date: Fri, 23 Nov 2007 17:08:15 +0000 [thread overview]
Message-ID: <20071123170815.GH31093@solarflare.com> (raw)
This is a net driver (and MTD driver, sfc_mtd) for our SFC4000 10G
Ethernet controller, branded "Solarstorm", with various PHYs. It is
intended to support our NIC reference designs SFE4001 (10GBASE-T),
SFE4002 (XFP), SFE4003 (10GBASE-CX4), OEM designs based on them, and
some development boards. We have been maintaining drivers out-of-tree
for some time but are now preparing them to work in-tree.
There are some issues that might need to be addressed:
1. When we enable NAPI polling, we need to set __LINK_STATE_START in
the net device used for NAPI. This bit is commented as private in
netdevice.h, but e1000 also does this. Is this incorrect?
2. We added a lot of definitions and code for 10G MDIO. This is mostly
generic and could be moved into core code.
We welcome review comments and are ready to address them.
The patch (against net-2.6.25) is at:
https://support.solarflare.com/netdev/net-2.6.25-sfc-2.2.0019.patch
The new files may also be downloaded as a tarball:
https://support.solarflare.com/netdev/net-2.6.25-sfc-2.2.0019.tar.gz
And for verification there is:
https://support.solarflare.com/netdev/MD5SUMS
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
next reply other threads:[~2007-11-23 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 17:08 Ben Hutchings [this message]
2007-11-28 6:09 ` [PATCH] [RFC] New driver "sfc" for Solarstorm SFC4000 controller Stephen Hemminger
2007-11-28 6:47 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 16:27 Robert Stonehouse
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=20071123170815.GH31093@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--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 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).