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
