From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Gallatin Subject: Re: [PATCH] myri10ge: improve port type reporting in ethtool output Date: Mon, 19 Oct 2009 09:30:39 -0400 Message-ID: <4ADC69FF.5000109@myri.com> References: <4ADBFA88.8030300@myri.com> <1255939929.3916.13.camel@localhost> <4ADC5CB8.4010801@myri.com> <1255957384.2782.2.camel@achroite> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Brice Goglin , "David S. Miller" , Linux Network Development list To: Ben Hutchings Return-path: Received: from mailbox2.myri.com ([64.172.73.26]:1855 "EHLO myri.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755948AbZJSNak (ORCPT ); Mon, 19 Oct 2009 09:30:40 -0400 In-Reply-To: <1255957384.2782.2.camel@achroite> Sender: netdev-owner@vger.kernel.org List-ID: Ben Hutchings wrote: > 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? Exactly. One has complained because drivers for other vendors NICs show this, even if they are fibre NICs or CX4 NICs, and don't actually support 10GbaseT. I'm happy to back this part out, and resubmit the patch without it. There is still some fairly valuable stuff in the patch -- mainly updating the NIC detection logic for new NICs to detect fibre vs copper. Drew