From: Shannon Nelson <snelson@pensando.io>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next 2/2] ionic: add devlink firmware update
Date: Thu, 3 Sep 2020 14:37:40 -0700 [thread overview]
Message-ID: <bd395a37-92b1-8d5f-eea5-66bb82a02e94@pensando.io> (raw)
In-Reply-To: <20200903125350.4bc345e9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 9/3/20 12:53 PM, Jakub Kicinski wrote:
> On Wed, 2 Sep 2020 12:57:17 -0700 Shannon Nelson wrote:
>> Add support for firmware update through the devlink interface.
>> This update copies the firmware object into the device, asks
>> the current firmware to install it, then asks the firmware to
>> set the device to use the new firmware on the next boot-up.
> Activate sounds too much like fw-active in Moshe's patches.
>
> Just to be clear - you're not actually switching from the current
> FW to the new one here, right?
>
> If it's more analogous to switching between flash images perhaps
> selecting would be a better term?
>
>> The install and activate steps are launched as asynchronous
>> requests, which are then followed up with status requests
>> commands. These status request commands will be answered with
>> an EAGAIN return value and will try again until the request
>> has completed or reached the timeout specified.
I think I can find a way to reword that - perhaps "enable" would be
better than "activate"?
Thanks,
sln
next prev parent reply other threads:[~2020-09-03 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 19:57 [PATCH net-next 0/2] ionic: add devlink dev flash support Shannon Nelson
2020-09-02 19:57 ` [PATCH net-next 1/2] ionic: update the fw update api Shannon Nelson
2020-09-02 19:57 ` [PATCH net-next 2/2] ionic: add devlink firmware update Shannon Nelson
2020-09-03 6:01 ` Jiri Pirko
2020-09-03 15:58 ` Shannon Nelson
2020-09-03 17:30 ` Jiri Pirko
2020-09-03 21:35 ` Shannon Nelson
2020-09-03 19:53 ` Jakub Kicinski
2020-09-03 21:37 ` Shannon Nelson [this message]
2020-09-03 21:45 ` Jakub Kicinski
2020-09-03 21:47 ` Shannon Nelson
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=bd395a37-92b1-8d5f-eea5-66bb82a02e94@pensando.io \
--to=snelson@pensando.io \
--cc=davem@davemloft.net \
--cc=kuba@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