netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 00/10] bnxt_en: Updates for net-next.
Date: Tue,  5 Apr 2016 04:22:32 -0400	[thread overview]
Message-ID: <1459844562-24576-1-git-send-email-michael.chan@broadcom.com> (raw)

Update to latest firmware interface, add EEE feature, unsupported SFP+
module warning, GEEPROM support, and ethtool -s improvements.

Michael Chan (9):
  bnxt_en: Update to Firmware 1.2.2 spec.
  bnxt_en: Improve flow control autoneg with Firmware 1.2.1 interface.
  bnxt_en: Add basic EEE support.
  bnxt_en: Add EEE setup code.
  bnxt_en: Add get_eee() and set_eee() ethtool support.
  bnxt_en: Set async event bits when registering with the firmware.
  bnxt_en: Add unsupported SFP+ module warnings.
  bnxt_en: Check for valid forced speed during ethtool -s.
  bnxt_en: Improve ethtool .get_settings().

Rob Swindell (1):
  bnxt_en: Provide NVM information via Ethtool GEEPROM

 drivers/net/ethernet/broadcom/bnxt/bnxt.c          | 259 ++++++++++--
 drivers/net/ethernet/broadcom/bnxt/bnxt.h          |  17 +-
 drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c  | 222 +++++++++--
 drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.h  |   4 +-
 drivers/net/ethernet/broadcom/bnxt/bnxt_fw_hdr.h   |   2 +-
 drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h      | 433 +++++++++++++++++++--
 drivers/net/ethernet/broadcom/bnxt/bnxt_nvm_defs.h |   2 +-
 drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c    |  14 +-
 drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.h    |   2 +-
 9 files changed, 855 insertions(+), 100 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2016-04-05  8:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  8:22 Michael Chan [this message]
2016-04-05  8:22 ` [PATCH net-next 01/10] bnxt_en: Update to Firmware 1.2.2 spec Michael Chan
2016-04-05  8:22 ` [PATCH net-next 02/10] bnxt_en: Improve flow control autoneg with Firmware 1.2.1 interface Michael Chan
2016-04-05  8:22 ` [PATCH net-next 03/10] bnxt_en: Add basic EEE support Michael Chan
2016-04-05  8:22 ` [PATCH net-next 04/10] bnxt_en: Add EEE setup code Michael Chan
2016-04-05  8:22 ` [PATCH net-next 05/10] bnxt_en: Add get_eee() and set_eee() ethtool support Michael Chan
2016-04-05 10:07   ` Ben Hutchings
2016-04-05 10:36     ` Michael Chan
2016-04-05 21:22       ` Ben Hutchings
2016-04-05  8:22 ` [PATCH net-next 06/10] bnxt_en: Set async event bits when registering with the firmware Michael Chan
2016-04-05  8:22 ` [PATCH net-next 07/10] bnxt_en: Add unsupported SFP+ module warnings Michael Chan
2016-04-05  8:22 ` [PATCH net-next 08/10] bnxt_en: Provide NVM information via Ethtool GEEPROM Michael Chan
2016-04-05  8:22 ` [PATCH net-next 09/10] bnxt_en: Check for valid forced speed during ethtool -s Michael Chan
2016-04-05  8:22 ` [PATCH net-next 10/10] bnxt_en: Improve ethtool .get_settings() Michael Chan
  -- strict thread matches above, loose matches on Subject: below --
2021-04-24 20:14 [PATCH net-next 00/10] bnxt_en: Updates for net-next Michael Chan
2017-07-24 16:34 Michael Chan
2017-07-25  0:32 ` David Miller
2016-02-25  8:19 [PATCH net-next 00/10] bnxt_en: updates " Michael Chan

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=1459844562-24576-1-git-send-email-michael.chan@broadcom.com \
    --to=michael.chan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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).