From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id EE4D2388F for ; Mon, 28 Nov 2016 02:16:48 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP; 27 Nov 2016 17:16:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,561,1473145200"; d="scan'208";a="196297527" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga004.fm.intel.com with ESMTP; 27 Nov 2016 17:16:47 -0800 Received: from fmsmsx118.amr.corp.intel.com (10.18.116.18) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sun, 27 Nov 2016 17:16:47 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx118.amr.corp.intel.com (10.18.116.18) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sun, 27 Nov 2016 17:16:47 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.239]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.142]) with mapi id 14.03.0248.002; Mon, 28 Nov 2016 09:16:45 +0800 From: "Lu, Wenzhuo" To: "Yigit, Ferruh" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH 00/16] e1000 base code update Thread-Index: AQHSRfKkC9da4Bc7706IBC0Run94WaDpJR6AgAR4+LA= Date: Mon, 28 Nov 2016 01:16:44 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093935348F@shsmsx102.ccr.corp.intel.com> References: <1479921780-9813-1-git-send-email-wenzhuo.lu@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 00/16] e1000 base code update X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2016 01:16:49 -0000 Hi Ferruh, > -----Original Message----- > From: Yigit, Ferruh > Sent: Friday, November 25, 2016 8:58 PM > To: Lu, Wenzhuo; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 00/16] e1000 base code update >=20 > Hi Wenzhuo, >=20 > On 11/23/2016 5:22 PM, Wenzhuo Lu wrote: > > Updated e1000 base code to fix several bugs and support > > i219 NICs. > > > > Wenzhuo Lu (16): > > e1000/base: increased ULP timer > > e1000/base: increase PHY PLL clock gate timing > > e1000/base: try more times to get HW mailbox lock > > e1000/base: add getting HW version support for i354 > > e1000/base: expose e1000_write_vfta_i350 > > e1000/base: add max RX jumbo frame define > > e1000/base: restore link speed after ULP exit > > e1000/base: clear ULP configuration register on ULP exit > > e1000/base: increase LANPHYPC low duration > > e1000/base: workaround for ULP entry flow > > e1000/base: enable new i219 devices > > e1000/base: always request clock during K1 at 1G link speed > > e1000/base: ability to force K1-off disabled > > e1000/base: support more i219 devices > > e1000/base: update readme > > e1000: add new i219 devices > > > > drivers/net/e1000/base/README | 4 +- > > drivers/net/e1000/base/e1000_82575.c | 1 - > > drivers/net/e1000/base/e1000_82575.h | 1 + > > drivers/net/e1000/base/e1000_api.c | 19 + > > drivers/net/e1000/base/e1000_defines.h | 9 + > > drivers/net/e1000/base/e1000_hw.h | 21 +- > > drivers/net/e1000/base/e1000_ich8lan.c | 865 > > +++++++++++++++++++++++++++++++-- > drivers/net/e1000/base/e1000_ich8lan.h | 21 +- > > drivers/net/e1000/base/e1000_mbx.c | 36 +- > > drivers/net/e1000/base/e1000_nvm.c | 1 + > > drivers/net/e1000/base/e1000_regs.h | 7 + > > drivers/net/e1000/em_ethdev.c | 34 +- > > 12 files changed, 949 insertions(+), 70 deletions(-) > > >=20 > Based on this pathset. >=20 > Can you also please send another patch to: > 1- add I219 to supported nics list > 2- announce new supported nic in release notes. >=20 > Also as far as I can see there is no igb/e1000 documentation under > doc/guides/nics/*, it can good to provide one, not with above requested > patches perhaps, but in some suitable time. I'll handle them. Thanks for the reminder :) >=20 > Thanks, > Ferruh