From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] nfp: extend speed capabilities advertised Date: Tue, 20 Dec 2016 10:25:59 +0000 Message-ID: References: <1482149104-40805-1-git-send-email-alejandro.lucero@netronome.com> <3dd84942-5c7b-5f3f-2760-a71f97dfcd6a@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: dev To: Alejandro Lucero Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 23566FB25 for ; Tue, 20 Dec 2016 11:26:01 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 12/19/2016 6:00 PM, Alejandro Lucero wrote: > I forgot one thing: to update the features file with this new one. > > I will wait for your feedback regarding the discussed problem for > sending another version. I think it is good to go, please send updated version. > <...> > > Sorry, confused. Is it like following: > > " > For new FW, there is no problem, it supports the range between > 1G - 50G, > and reports correct current speed. > > With old FW, device still can be set to speed range between 1G - > 50G, > but it doesn't report current speed correct, and DPDK driver reports > back to application as device current speed is 40G, without really > knowing the current speed. > " > > > Yes, that is. Should then I do anything else or the patch is right > for you now? So, this patch is correct. But for the previous patch "net/nfp: report link speed using hardware info", it would be nice to add above information into source as comment and into commit log. If you can, would you mind sending a new version of that patch? Thanks, ferruh > <...>