From: Ben Hutchings <bhutchings@solarflare.com>
To: Andrew Gallatin <gallatin@myri.com>
Cc: Brice Goglin <brice@myri.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: [PATCH] myri10ge: improve port type reporting in ethtool output
Date: Mon, 19 Oct 2009 14:03:04 +0100 [thread overview]
Message-ID: <1255957384.2782.2.camel@achroite> (raw)
In-Reply-To: <4ADC5CB8.4010801@myri.com>
On Mon, 2009-10-19 at 08:34 -0400, Andrew Gallatin wrote:
> Ben Hutchings wrote:
>
> > Lying about link modes is not an improvement.
>
> OK, so we're probably doing something wrong. I suspect we're not
> alone. At least we don't set SUPPORTED_TP for CX4, like I've
> seen some NICs do.
>
> Can somebody suggest how we can tell ethtool that
> the NIC supports 10Gb only (no autoneg down to 1Gb or lower)
> for copper (10Gbase-CX4)? How about for fiber (10Gbase-{S,L})R?
What's wrong with what you already do? Customers expect to see
something on the supported line?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-10-19 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 5:35 [PATCH] myri10ge: improve port type reporting in ethtool output Brice Goglin
2009-10-19 8:12 ` Ben Hutchings
2009-10-19 12:34 ` Andrew Gallatin
2009-10-19 13:03 ` Ben Hutchings [this message]
2009-10-19 13:30 ` Andrew Gallatin
2009-10-19 14:17 ` Ben Hutchings
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=1255957384.2782.2.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=brice@myri.com \
--cc=davem@davemloft.net \
--cc=gallatin@myri.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 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.