From: Mark Starovoytov <mstarovoitov@marvell.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Igor Russkikh <irusskikh@marvell.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Mark Starovoytov <mstarovoitov@marvell.com>
Subject: [PATCH net-next 0/2] net: atlantic: add support for FW 4.x
Date: Fri, 17 Jul 2020 21:01:45 +0300 [thread overview]
Message-ID: <20200717180147.8854-1-mstarovoitov@marvell.com> (raw)
This patch set adds support for FW 4.x, which is about to get into the
production for some products.
4.x is mostly compatible with 3.x, save for soft reset, which requires
the acquisition of 2 additional semaphores.
Other differences (e.g. absence of PTP support) are handled via
capabilities.
Note: 4.x targets specific products only. 3.x is still the main firmware
branch, which should be used by most users (at least for now).
Dmitry Bogdanov (1):
net: atlantic: add support for FW 4.x
Mark Starovoytov (1):
net: atlantic: align return value of ver_match function with function
name
.../aquantia/atlantic/hw_atl/hw_atl_llh.c | 17 +++++-
.../aquantia/atlantic/hw_atl/hw_atl_llh.h | 10 +++-
.../atlantic/hw_atl/hw_atl_llh_internal.h | 11 +++-
.../aquantia/atlantic/hw_atl/hw_atl_utils.c | 58 +++++++++++++------
.../aquantia/atlantic/hw_atl/hw_atl_utils.h | 2 +-
.../aquantia/atlantic/hw_atl2/hw_atl2_utils.c | 3 +-
6 files changed, 70 insertions(+), 31 deletions(-)
--
2.25.1
next reply other threads:[~2020-07-17 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:01 Mark Starovoytov [this message]
2020-07-17 18:01 ` [PATCH net-next 1/2] net: atlantic: align return value of ver_match function with function name Mark Starovoytov
2020-07-17 18:01 ` [PATCH net-next 2/2] net: atlantic: add support for FW 4.x Mark Starovoytov
2020-07-18 2:01 ` [PATCH net-next 0/2] " 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=20200717180147.8854-1-mstarovoitov@marvell.com \
--to=mstarovoitov@marvell.com \
--cc=davem@davemloft.net \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).