From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: announce end of support for some Broadcom devices
Date: Mon, 26 Oct 2020 14:46:04 -0700 [thread overview]
Message-ID: <20201026214604.35570-1-ajit.khaparde@broadcom.com> (raw)
Devices belonging to BCM573xx and BCM5740x family will not be supported
from the 21.02 release.
Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 2e082499b8..f1fce4210d 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -166,3 +166,9 @@ Deprecation Notices
``make``. Given environments are too much variables for such a simple script,
it will be removed in DPDK 20.11.
Some useful parts may be converted into specific scripts.
+
+* Broadcom bnxt PMD: NetXtreme devices belonging to the ``BCM573xx and
+ BCM5740x`` families will no longer be supported as of DPDK 21.02.
+ Specifically the support for the following Broadcom PCI ids will be removed
+ from the release: ``0x16c8, 0x16c9, 0x16ca, 0x16ce, 0x16cf, 0x16df,``
+ ``0x16d0, 0x16d1, 0x16d2, 0x16d4, 0x16d5, 0x16e7, 0x16e8, 0x16e9``.
--
2.21.1 (Apple Git-122.3)
next reply other threads:[~2020-10-26 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 21:46 Ajit Khaparde [this message]
2020-11-03 10:50 ` Kevin Traynor
2020-11-03 17:26 ` Ajit Khaparde
2020-11-06 19:22 ` Kevin Traynor
2020-11-06 20:59 ` Ajit Khaparde
2020-11-20 17:30 ` Ajit Khaparde
2020-11-22 20:15 ` Thomas Monjalon
2020-11-23 14:56 ` Ajit Khaparde
2020-11-24 15:34 ` Ferruh Yigit
2020-11-25 8:48 ` Jerin Jacob
2020-11-26 11:31 ` Bruce Richardson
2020-11-26 16:52 ` 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=20201026214604.35570-1-ajit.khaparde@broadcom.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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).