Bug#955310: u-boot-tools: update list of architectures in mkimage

2022-10-19 Thread Diederik de Haas
On 29 Mar 2020 12:33:40 -0700 Vagrant Cascadian  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.


Bug#955310: u-boot-tools: update list of architectures in mkimage

2020-03-29 Thread Vagrant Cascadian
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
  alphaAlpha
  arc  ARC
  arm  ARM
  arm64AArch64
...
  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


signature.asc
Description: PGP signature


Bug#955310: u-boot-tools: update list of architectures in mkimage

2020-03-29 Thread Chris Dumont
Package: u-boot-tools
Version: 2019.01+dfsg-7
Severity: minor

Dear Maintainer,

   * What led up to the situation?
read the manpage for mkimage and then used 'mkimage -T -h'
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
N/A
   * 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
...

   * What outcome did you expect instead?

I had hoped for one or more lines for ARM. I found this out because I don't 
know if I should use 'arm' which fits all types of ARM or an 
architecture-specific form such as 'arm64' or 'aarch64'.
   $ mkimage -T -h

Invalid image type, supported are:
Unknown image type  Unknown image type
aisimage Davinci AIS image
arm  ARM image
arm64(if necessary)
armv71   (if necessary)
armel(if necessary)
armhf(if necessary)
atmelimage   ATMEL ROM-Boot Image
filesystem   Filesystem Image
...

-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates')
Architecture: arm64 (aarch64)

Kernel: Linux 5.4.28-sunxi64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages u-boot-tools depends on:
ii  libc6  2.28-10