From: Ben Greear <greearb@candelatech.com>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: Benny Amorsen <benny+usenet@amorsen.dk>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC?
Date: Wed, 18 Jan 2012 14:43:22 -0800 [thread overview]
Message-ID: <4F174B0A.10208@candelatech.com> (raw)
In-Reply-To: <1326925160.2795.45.camel@probook>
On 01/18/2012 02:19 PM, Jesper Dangaard Brouer wrote:
> On Wed, 2012-01-18 at 22:45 +0100, Benny Amorsen wrote:
>> Jesse Brandeburg<jesse.brandeburg@intel.com> writes:
>>
>>> For X520 adapters, the documentation[1] states that which SFP+
>>> adapters are/are not supported. Direct attach cables are also
>>> supported.
>>>
>>> [1] http://www.intel.com/support/network/adapter/pro100/sb/CS-030612.htm
>>
>> I can't believe that locked optics have now arrived on commodity
>> hardware. I have been trying to migrate to all-Intel networking at work;
>> that effort is certainly on hold now.
>
> I cannot understand why Intel are pulling a stunt like this! :-(
>
> I have read the code, and the limitation comes from a EEPROM setting on
> the NIC, see define "IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP 0x1".
>
> Here is a (untested) patch I believe removes the limitation in the
> driver:
>
>
> [PATCH] ixgbe: Always allow any SFP+ regardless of EEPROM setting.
>
> Intel are trying to limit which SFP's we can use in our NICs.
> We don't like this practices in the Linux Kernel.
I think that you should at least print some big warnings in
the kernel logs if you do this, as well as all the info you
can find on the non-supported SFP+ module in use so that folks can debug
things if the SFP+ doesn't properly work.
As previously mentioned, I found a case where some random SFP+
did NOT work with a similar hack in place...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-01-18 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 11:30 ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC? Jesper Dangaard Brouer
2012-01-18 17:13 ` Jesse Brandeburg
2012-01-18 20:00 ` Jesper Dangaard Brouer
2012-01-18 21:45 ` Benny Amorsen
2012-01-18 22:19 ` Jesper Dangaard Brouer
2012-01-18 22:43 ` Ben Greear [this message]
2012-01-19 14:46 ` [PATCH RFC] ixgbe: Module param "allow_any_sfp" for allowing unsupported SFP+ modules Jesper Dangaard Brouer
2012-01-20 1:12 ` Jeff Kirsher
2012-01-18 22:21 ` [E1000-devel] ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC? Fujinaka, Todd
2012-01-18 22:40 ` Ben Greear
2012-01-19 11:50 ` David Lamparter
2012-01-19 1:12 ` [E1000-devel] " Chuck Anderson
2012-01-19 2:55 ` Simon Chen
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=4F174B0A.10208@candelatech.com \
--to=greearb@candelatech.com \
--cc=benny+usenet@amorsen.dk \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=hawk@comx.dk \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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.