From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: Bug#955310: u-boot-tools: update list of architectures in mkimage
Date: Sun, 29 Mar 2020 12:33:40 -0700 [thread overview]
Message-ID: <87h7y7vtuz.fsf@ponder> (raw)
In-Reply-To: <0608344D-DE7D-4633-9E40-63C5D7D3227D@lindadumont.biz>
On 2020-03-29, Chris Dumont wrote:
> * What led up to the situation?
> read the manpage for mkimage and then used 'mkimage -T -h'
...
> * What was the outcome of this action?
> The output (ellipsized)
>
> $ mkimage -T -h
>
> Invalid image type, supported are:
> Unknown image type Unknown image type
> aisimage Davinci AIS image
> atmelimage ATMEL ROM-Boot Image
> filesystem Filesystem Image
> ...
It appears the recommendation from mkimage help output is to use
"mkimage -T list" now.
It seems like this should be changed to "-T list" in the manpage.
There are several other options -A, -O and -C that also should probably
be updated, but those options need an updated to the code as well, as
they output the usage information in addition to listing the available
Architecture/Os/Compression types:
$ mkimage -A list
Invalid architecture, supported are:
Unknown architecture Unknown architecture
Unknown architecture Unknown architecture
alpha Alpha
arc ARC
arm ARM
arm64 AArch64
...
x86_64 AMD x86_64
xtensa Xtensa
Error: Invalid architecture
Usage: mkimage -l image
-l ==> list image header information
mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name
-d data_file[:data_file...] image
-A ==> set architecture to 'arch'
...
-i => input filename for ramdisk file
Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
Using "mkimage -T list" just displays the list of image types, from what
I can tell, which seems more-or-less fine.
I haven't tested anything newer than 2020.04~rc2, so there may be newer
fixes upstream...
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200329/d5f14cca/attachment.sig>
parent reply other threads:[~2020-03-29 19:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0608344D-DE7D-4633-9E40-63C5D7D3227D@lindadumont.biz>]
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=87h7y7vtuz.fsf@ponder \
--to=vagrant@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.