From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 0/6] bnxt_en: Add support for NS2 Nitro.
Date: Mon, 18 Jul 2016 07:15:19 -0400 [thread overview]
Message-ID: <1468840525-340-1-git-send-email-michael.chan@broadcom.com> (raw)
This series adds support for the embedded version of the
ethernet controller (Nitro) in the North Star 2 SoC. There are a number
of features not supported and a software workaround for a hardware rx
bug is required for Nitro A0. Please review.
Prashant Sreedharan (6):
bnxt_en: Add basic support for Nitro in North Star 2.
bnxt_en: Workaround Nitro A0 hardware RX bug (part 1).
bnxt_en: Workaround Nitro A0 hardware RX bug (part 2).
bnxt_en: Workaround Nitro A0 hardware RX bug (part 3).
bnxt_en: Workaround Nitro A0 RX hardware bug (part 4).
bnxt_en: Add BCM58700 PCI device ID for NS2 Nitro.
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 254 ++++++++++++++++++----
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 6 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 12 +-
3 files changed, 229 insertions(+), 43 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-07-18 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:15 Michael Chan [this message]
2016-07-18 11:15 ` [PATCH net-next 1/6] bnxt_en: Add basic support for Nitro in North Star 2 Michael Chan
2016-07-18 11:15 ` [PATCH net-next 2/6] bnxt_en: Workaround Nitro A0 hardware RX bug (part 1) Michael Chan
2016-07-18 11:15 ` [PATCH net-next 3/6] bnxt_en: Workaround Nitro A0 hardware RX bug (part 2) Michael Chan
2016-07-18 11:15 ` [PATCH net-next 4/6] bnxt_en: Workaround Nitro A0 hardware RX bug (part 3) Michael Chan
2016-07-18 11:15 ` [PATCH net-next 5/6] bnxt_en: Workaround Nitro A0 RX hardware bug (part 4) Michael Chan
2016-07-18 11:15 ` [PATCH net-next 6/6] bnxt_en: Add BCM58700 PCI device ID for NS2 Nitro Michael Chan
2016-07-19 23:29 ` [PATCH net-next 0/6] bnxt_en: Add support " David Miller
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=1468840525-340-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).