From: Alex Forster <alex@alexforster.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question about unsupported transceivers
Date: Thu, 15 Oct 2015 14:46:29 +0000 [thread overview]
Message-ID: <D2443E39.28D8%alex@alexforster.com> (raw)
In-Reply-To: <561D6AD2.9000308@gmail.com>
On 10/13/15, 4:34 PM, "Alexander Duyck" <alexander.duyck@gmail.com> wrote:
>If you are using Intel's out-of-tree ixgbe driver I believe the module
>parameters are comma separated with one index per port. So if you have
>two ports you should be passing "allow_unsupported_sfp=1,1", and for 4
>you would need four '1's.
This seemed very promising. I compiled and installed the out of tree ixgbe
driver and set the option in /etc/modprobe.d/ixgbe.conf. dmesg shows all
eight "allow_unsupported_sfp enabled" messages but the last four ports
still error out with the unsupported SFP message when running the tests.
Before I start arbitrarily trying to patch out parts of the SFP
verification code in ixgbe, are there any other tips I should know?
Alex Forster
next prev parent reply other threads:[~2015-10-15 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 17:22 Alex Forster
2015-10-13 18:57 ` Alex Forster
2015-10-13 20:34 ` Alexander Duyck
2015-10-15 14:46 ` Alex Forster [this message]
2015-10-15 15:30 ` Alexander Duyck
2015-10-15 15:33 ` Alex Forster
2015-10-15 15:43 Alex Forster
2015-10-15 16:17 ` Alexander Duyck
2015-10-15 17:13 ` Alex Forster
2015-10-15 18:00 ` Alexander Duyck
2015-10-15 18:29 ` Alex Forster
2015-10-15 19:53 ` Alexander Duyck
2015-10-19 1:06 ` Alex Forster
2015-10-19 15:08 ` Alexander Duyck
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=D2443E39.28D8%alex@alexforster.com \
--to=alex@alexforster.com \
--cc=alexander.duyck@gmail.com \
--cc=dev@dpdk.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).