summaryrefslogtreecommitdiffstats
path: root/Documentation/nvme-fw-download.txt
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-24 07:57:54 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-12-24 07:57:54 +0000
commit66e4b69042cd3b44acd42f1fad2109180c1bc48b (patch)
tree8bd8e664ae856167566375357963062e8112f181 /Documentation/nvme-fw-download.txt
parentReleasing debian version 2.5-1. (diff)
downloadnvme-cli-66e4b69042cd3b44acd42f1fad2109180c1bc48b.tar.xz
nvme-cli-66e4b69042cd3b44acd42f1fad2109180c1bc48b.zip
Merging upstream version 2.7.1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/nvme-fw-download.txt')
-rw-r--r--Documentation/nvme-fw-download.txt16
1 files changed, 13 insertions, 3 deletions
diff --git a/Documentation/nvme-fw-download.txt b/Documentation/nvme-fw-download.txt
index 84e407e..1ec466f 100644
--- a/Documentation/nvme-fw-download.txt
+++ b/Documentation/nvme-fw-download.txt
@@ -9,8 +9,9 @@ SYNOPSIS
--------
[verse]
'nvme fw-download' <device> [--fw=<firmware-file> | -f <firmware-file>]
- [--xfer=<transfer-size> | -x <transfer-size>]
- [--offset=<offset> | -o <offset>]
+ [--xfer=<transfer-size> | -x <transfer-size>]
+ [--offset=<offset> | -O <offset>]
+ [--output-format=<fmt> | -o <fmt>] [--verbose | -v]
DESCRIPTION
-----------
@@ -48,13 +49,22 @@ OPTIONS
the device has a max transfer size requirement for firmware. It
defaults to 4k.
--o <offset>::
+-O <offset>::
--offset=<offset>::
This specifies the starting offset in dwords. This is really only
useful if your firmware is split in multiple files; otherwise
the offset starts at zero and automatically adjusts based on the
'xfer' size given.
+-o <fmt>::
+--output-format=<fmt>::
+ Set the reporting format to 'normal', 'json' or 'binary'. Only one
+ output format can be used at a time.
+
+-v::
+--verbose::
+ Increase the information detail in the output.
+
EXAMPLES
--------
* Transfer a firmware size 128KiB at a time: