On 29 Mar 2020 12:33:40 -0700 Vagrant Cascadian <vagr...@debian.org> wrote: > 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 ... > > 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...
I checked it with version 2022.10+dfsg-1 and AFAICT both command help and the manpage have the mentioned options documented. Chris, do you consider this bug fixed?
signature.asc
Description: This is a digitally signed message part.
