Comment 9 for bug 1869441

Revision history for this message
dann frazier (dannf) wrote :

= Command usage analysis =
Summary - the -proposed usage statements all describe a superset of the commands/arguments in the previous version, with one exception. In bionic, mstflint's -qq argument used to say it affected both the burn and query commands - but the -proposed version only claims to impact query. The upstream commit that made this change is a 17K line diff that just says "Porting MFT-4.9.0 changes":
  https://github.com/Mellanox/mstflint/commit/58bc68152b0f45200868299c03cadab1b985fdc7
I don't see anything in that commit that obviously changes when that parameter is used - I'll need to ask Mellanox to advise.

== eoan ==
=== mstconfig ===
Usage diff just adds a "DESCRIPTION" section, no OPTION changes.
=== mstflint ===
Supports all old arguments. Adds --latest_fw, --ir, --low-cpu and --flashed_version. Also adds image_reactivate and binary_compare subcommands.
=== mstmcra ===
Usage diff just adds a "DESCRIPTION" section, no OPTION changes.

== bionic ==
=== mstconfig ===
Usage diff just adds a "DESCRIPTION" section, no OPTION changes.
=== mstflint ===
Supports all old arguments. Adds --latest_fw, --ir, --low-cpu --flashed_version, --private_key2, --hmac_key & --key_uuid2.

** -qq used to say it impacted both burn and query commands, now just query. why? **

Also adds sign_with_hmac, image_reactivate and binary_compare commands.
=== mstmcra ===
No functional changes in --usage, just a new description & some cleanup.

=== mstmtserver ===
Adds a -v[ersion].

=== mstvpf ===
Adds a -r argument (doesn't say why)