From 66e4b69042cd3b44acd42f1fad2109180c1bc48b Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sun, 24 Dec 2023 08:57:54 +0100
Subject: Merging upstream version 2.7.1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 Documentation/nvme-fw-download.txt | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

(limited to 'Documentation/nvme-fw-download.txt')

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:
-- 
cgit v1.2.3