From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 3/4] net/ixgbe: add firmware version get Date: Wed, 4 Jan 2017 12:01:36 +0000 Message-ID: <54697cc6-0b6d-18f7-0cc0-cb7000a280ab@intel.com> References: <1481008582-69416-1-git-send-email-qiming.yang@intel.com> <1482841816-54143-1-git-send-email-qiming.yang@intel.com> <1482841816-54143-4-git-send-email-qiming.yang@intel.com> <9c401d90-0264-8fc8-3733-abb59bfd277e@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: "Horton, Remy" To: "Yang, Qiming" , "dev@dpdk.org" , "thomas.monjalon@6wind.com" Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 576EF2C01 for ; Wed, 4 Jan 2017 13:01:39 +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 1/4/2017 9:48 AM, Yang, Qiming wrote: > Yes, etrack_id is an unique value. But not all NICs have this value. > I didn't find any value about fw version in fm10k. Yes, you are right, following is from i40e datasheet: " The EEPROM Manager tool writes a unique 32-bit eTrack_ID number in two sequential NVM words. The eTrack_ID is written when EEPROM Manager tool creates an image on the Intel network. The eTrack_ID DB tracks NVM images back to a specific SCM build " So it is unique, and can be used to identify FW version. And yes it can be enough on its own without having major minor FW version fields. > I40e is 8 bit too. > firmware-version: 5.04 0x800024ca Right, I read it wrong, i40e also has 32bits etrack-id. Thanks, ferruh