From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/16] e1000 base code update
Date: Fri, 25 Nov 2016 12:58:05 +0000 [thread overview]
Message-ID: <b3bc9072-3532-544d-5c59-219eae9d56e3@intel.com> (raw)
In-Reply-To: <1479921780-9813-1-git-send-email-wenzhuo.lu@intel.com>
Hi Wenzhuo,
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(-)
>
Based on this pathset.
Can you also please send another patch to:
1- add I219 to supported nics list
2- announce new supported nic in release notes.
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.
Thanks,
ferruh
next prev parent reply other threads:[~2016-11-25 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:22 Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 01/16] e1000/base: increased ULP timer Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 02/16] e1000/base: increase PHY PLL clock gate timing Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 03/16] e1000/base: try more times to get HW mailbox lock Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 04/16] e1000/base: add getting HW version support for i354 Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 05/16] e1000/base: expose e1000_write_vfta_i350 Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 06/16] e1000/base: add max RX jumbo frame define Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 07/16] e1000/base: restore link speed after ULP exit Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 08/16] e1000/base: clear ULP configuration register on " Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 09/16] e1000/base: increase LANPHYPC low duration Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 10/16] e1000/base: workaround for ULP entry flow Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 11/16] e1000/base: enable new i219 devices Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 12/16] e1000/base: always request clock during K1 at 1G link speed Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 13/16] e1000/base: ability to force K1-off disabled Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 14/16] e1000/base: support more i219 devices Wenzhuo Lu
2016-11-23 17:22 ` [dpdk-dev] [PATCH 15/16] e1000/base: update readme Wenzhuo Lu
2016-11-23 17:23 ` [dpdk-dev] [PATCH 16/16] e1000: add new i219 devices Wenzhuo Lu
2016-11-25 12:54 ` [dpdk-dev] [PATCH 00/16] e1000 base code update Ferruh Yigit
2016-11-28 1:15 ` Lu, Wenzhuo
2016-11-25 12:58 ` Ferruh Yigit [this message]
2016-11-28 1:16 ` Lu, Wenzhuo
2016-11-28 11:33 ` Thomas Monjalon
2016-11-29 0:30 ` Lu, Wenzhuo
2016-11-29 9:28 ` Thomas Monjalon
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=b3bc9072-3532-544d-5c59-219eae9d56e3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).