diff options
| author | Danielle Ratson <danieller@nvidia.com> | 2024-06-27 17:08:55 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2024-06-28 10:48:23 +0100 |
| commit | c4f78134d45c9619339c96b4bea380b1d0699788 (patch) | |
| tree | 4a42d486abf06902c18253e2358c4d01082548c0 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | a39c84d796254e6b1662ca0c46dbc313379e9291 (diff) | |
| download | linux-c4f78134d45c9619339c96b4bea380b1d0699788.tar.gz linux-c4f78134d45c9619339c96b4bea380b1d0699788.tar.bz2 linux-c4f78134d45c9619339c96b4bea380b1d0699788.zip | |
ethtool: cmis_fw_update: add a layer for supporting firmware update using CDB
According to the CMIS standard, the firmware update process is done using
a CDB commands sequence.
Implement a work that will be triggered from the module layer in the
next patch the will initiate and execute all the CDB commands in order, to
eventually complete the firmware update process.
This flashing process includes, writing the firmware image, running the new
firmware image and committing it after testing, so that it will run upon
reset.
This work will also notify user space about the progress of the firmware
update process.
Signed-off-by: Danielle Ratson <danieller@nvidia.com>
Reviewed-by: Petr Machata <petrm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions