[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f6d5d039-420a-21d7-2796-0d54292744dc@marvell.com>
Date: Sun, 23 Aug 2020 13:57:51 +0300
From: Igor Russkikh <irusskikh@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, "David S . Miller" <davem@...emloft.net>,
"Ariel Elior" <aelior@...vell.com>,
Michal Kalderon <mkalderon@...vell.com>
Subject: Re: [EXT] Re: [PATCH v6 net-next 04/10] qed: implement devlink info
request
>> ~$ sudo ~/iproute2/devlink/devlink dev info
>> pci/0000:01:00.1:
>> driver qed
>> board.serial_number REE1915E44552
>> versions:
>> running:
>> fw.app 8.42.2.0
>> stored:
>> fw.mgmt 8.52.10.0
>
> Are you not able to report the running version of the stored firmware?
> The two sections are used for checking if machine needs fw-activation
> or reboot (i.e. if fw.mgmt in stored section does not match fw.mgmt in
> running - there is a new FW to activate).
Right now I think its not possible.
Will investigate more later, when we'll dive more into FW related
implementation of devlink APIs.
> In general looks good:
>
> Reviewed-by: Jakub Kicinski <kuba@...nel.org>
>
Thanks
Powered by blists - more mailing lists