From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Sean Anderson <seanga2@gmail.com>, u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v2 14/14] doc: Add man page for dumpimage
Date: Thu, 16 Jun 2022 13:50:54 +0200 [thread overview]
Message-ID: <985a8767-2e31-ec86-54a8-f093fe65a378@gmx.de> (raw)
In-Reply-To: <20220612221411.1608406-15-seanga2@gmail.com>
On 6/13/22 00:14, Sean Anderson wrote:
> This tool seems a bit underloved. Unfortunately, it seems to be missing
> support for FIT images. Alas...
>
> Add a man page documenting it. The example is taken from commit a804b5ce2d
> ("Add dumpimage, a tool to extract data from U-Boot images").
>
> Signed-off-by: Sean Anderson <seanga2@gmail.com>
> ---
>
> Changes in v2:
> - Ensure comments are requests
>
> doc/dumpimage.1 | 103 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 doc/dumpimage.1
>
> diff --git a/doc/dumpimage.1 b/doc/dumpimage.1
> new file mode 100644
> index 0000000000..52a45a3404
> --- /dev/null
> +++ b/doc/dumpimage.1
> @@ -0,0 +1,103 @@
> +.\" SPDX-License-Identifier: GPL-2.0
> +.\" Copyright (C) 2022 Sean Anderson <seanga2@gmail.com>
> +.TH DUMPIMAGE 1 2022-06-11 U-Boot
> +.SH NAME
> +dumpimage \- extract data from U-Boot images
> +.
> +.SH SYNOPSIS
> +.SY dumpimage
> +.OP \-T type
> +.BI \-l\~ image
> +.YS
> +.SY dumpimage
> +.OP \-T type
The online help shows this parameter as optional.
> +.OP \-p position
-p is optional so it should be in brackets.
> +.BI \-o\~ outfile
-o is optional.
Best regards
Heinrich
> +.I image
> +.YS
> +.SY dumpimage
> +.B \-h
> +.YS
> +.SY dumpimage
> +.B \-V
> +.YS
> +.
> +.SH DESCRIPTION
> +.B dumpimage
> +lists and extracts data from U-Boot images. If
> +.B \-l
> +is specified,
> +.B dumpimage
> +lists the components in
> +.IR image .
> +Otherwise,
> +.B dumpimage
> +extracts the component at
> +.IR position " to " outfile .
> +.
> +.SH OPTIONS
> +.TP
> +.B \-h
> +Print usage information and exit.
> +.
> +.TP
> +.B \-l
> +Print the header information for
> +.IR image ,
> +including a list of components.
> +.
> +.TP
> +.BI \-o " outfile"
> +The file to write the dumped component to.
> +.TP
> +.BI \-p " position"
> +Specify the
> +.I position
> +of the component to dump. This should be a numeric index, starting at 0. If not
> +specified, the default
> +.I position
> +is 0.
> +.
> +.TP
> +.BI \-T " type"
> +Specify the
> +.I type
> +of the image. If not specified, the image type will be automatically detected. A
> +list of supported image types may be printed by running
> +.BR "mkimage\~\-T\~list" .
> +.
> +.TP
> +.B \-V
> +Print version information and exit.
> +.
> +.SH BUGS
> +Please report bugs to the
> +.UR https://\:source\:.denx\:.de/\:u-boot/\:u-boot/\:issues
> +U-Boot bug tracker
> +.UE .
> +.SH EXAMPLES
> +Create a multi-file image and then extract part of that image
> +.PP
> +.EX
> +.in +4
> +$ \c
> +.B mkimage \-A x86 \-O linux \-T multi \-n x86 \\\\\&
> +.in +4
> +.B \-d vmlinuz:initrd.img:System.map multi.img
> +.in
> +Image Name: x86
> +Created: Thu Jul 25 10:29:13 2013
> +Image Type: Intel x86 Linux Multi-File Image (gzip compressed)
> +Data Size: 13722956 Bytes = 13401.32 kB = 13.09 MB
> +Load Address: 00000000
> +Entry Point: 00000000
> +Contents:
> + Image 0: 4040128 Bytes = 3945.44 kB = 3.85 MB
> + Image 1: 7991719 Bytes = 7804.41 kB = 7.62 MB
> + Image 2: 1691092 Bytes = 1651.46 kB = 1.61 MB
> +$ \c
> +.B dumpimage -p 2 -o System.map multi.img
> +.EE
> +.in
> +.SH SEE ALSO
> +.BR mkimage (1)
next prev parent reply other threads:[~2022-06-16 11:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 22:13 [PATCH v2 00/14] doc: mkimage: Rework and refactor the man page; add long options Sean Anderson
2022-06-12 22:13 ` [PATCH v2 01/14] doc: mkimage: Use standard style for synopsis Sean Anderson
2022-06-16 9:45 ` Heinrich Schuchardt
2022-06-16 13:40 ` Sean Anderson
2022-06-12 22:13 ` [PATCH v2 02/14] doc: mkimage: Use empty request instead of blank lines Sean Anderson
2022-06-12 22:14 ` [PATCH v2 03/14] doc: mkimage: Reformat examples Sean Anderson
2022-06-12 22:14 ` [PATCH v2 04/14] doc: mkimage: Regularize option documentation Sean Anderson
2022-06-16 10:00 ` Heinrich Schuchardt
2022-06-16 13:42 ` Sean Anderson
2022-06-12 22:14 ` [PATCH v2 05/14] doc: mkimage: Use subsection macro Sean Anderson
2022-06-16 10:08 ` Heinrich Schuchardt
2022-06-16 13:45 ` Sean Anderson
2022-06-12 22:14 ` [PATCH v2 06/14] doc: mkimage: Rearrange/remove some options Sean Anderson
2022-06-12 22:14 ` [PATCH v2 07/14] doc: mkimage: Use correct capitalization for NAME Sean Anderson
2022-06-12 22:14 ` [PATCH v2 08/14] doc: mkimage: Edit options for style and consistency Sean Anderson
2022-06-12 22:14 ` [PATCH v2 09/14] doc: mkimage: Add BUGS section Sean Anderson
2022-06-12 22:14 ` [PATCH v2 10/14] doc: mkimage: Add SEE ALSO section Sean Anderson
2022-06-12 22:14 ` [PATCH v2 11/14] doc: mkimage: Remove AUTHORS section Sean Anderson
2022-06-12 22:14 ` [PATCH v2 12/14] mkimage: Add long options Sean Anderson
2022-06-12 22:14 ` [PATCH v2 13/14] doc: mkimage: Further document -o and -R Sean Anderson
2022-06-12 22:14 ` [PATCH v2 14/14] doc: Add man page for dumpimage Sean Anderson
2022-06-16 11:50 ` Heinrich Schuchardt [this message]
2022-06-16 13:47 ` Sean Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=985a8767-2e31-ec86-54a8-f093fe65a378@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).