netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, idosch@mellanox.com, yotamg@mellanox.com,
	mlxsw@mellanox.com, Yuval.Mintz@cavium.com
Subject: Re: [patch net-next v2 0/8] mlxsw: Support firmware flash
Date: Wed, 24 May 2017 16:33:28 -0400 (EDT)	[thread overview]
Message-ID: <20170524.163328.672261790569871029.davem@davemloft.net> (raw)
In-Reply-To: <20170523195630.6460-1-jiri@resnulli.us>

From: Jiri Pirko <jiri@resnulli.us>
Date: Tue, 23 May 2017 21:56:22 +0200

> From: Jiri Pirko <jiri@mellanox.com>
> 
> Add support for device firmware flash on mlxsw spectrum. The firmware files
> are expected to be in the Mellanox Firmware Archive version 2 (MFA2)
> format.
> 
> The firmware flash is triggered on driver initialization time if the device
> firmware version does not meet the minimum firmware version supported by
> the driver.
> 
> Currently, to activate the newly flashed firmware, the user needs to
> reboot his system.
> 
> The first patch introduces the mlxfw module, which implements common logic
> needed for the firmware flash process on Mellanox products, such as the
> MFA2 format parsing and the firmware flash state machine logic. As the
> module implements common logic which will be needed by various different
> Mellanox drivers, it defines a set of callbacks needed to interact with the
> specific device.
> 
> Patches 1-5 implement the needed mlxfw callbacks in the mlxsw spectrum
> driver.
> 
> Patches 6 and 7 add boot-time firmware upgrade on the mlxsw spectrum
> driver.
> 
> Patch 8 adds a fix needed for new firmware versions.

Series applied, although I hope you sort out the user interface
soon otherwise most of this is completely dead unused code.

Thanks.

  parent reply	other threads:[~2017-05-24 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 19:56 [patch net-next v2 0/8] mlxsw: Support firmware flash Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 1/8] Add the mlxfw module for Mellanox firmware flash process Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 2/8] mlxsw: reg: Add Management Component Query Information register Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 3/8] mlxsw: reg: Add Management Component Control register Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 4/8] mlxsw: reg: Add Management Component Data Access register Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 5/8] mlxsw: spectrum: Add the needed callbacks for mlxfw integration Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 6/8] mlxsw: core: Create the mlxsw_fw_rev struct Jiri Pirko
2017-05-23 19:56 ` [patch net-next v2 7/8] mlxsw: spectrum: Validate firmware revision on init Jiri Pirko
2017-05-24  5:42   ` Ido Schimmel
2017-05-23 19:56 ` [patch net-next v2 8/8] mlxsw: spectrum_router: Adjust RIF configuration for new firmware versions Jiri Pirko
2017-05-24 20:33 ` David Miller [this message]
2017-05-25  6:15   ` [patch net-next v2 0/8] mlxsw: Support firmware flash Jiri Pirko

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=20170524.163328.672261790569871029.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Yuval.Mintz@cavium.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=yotamg@mellanox.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).