On Wed, 16 Jun 2010 10:38:24 +0900 Nobuhiro Iwamatsu <iwama...@nigauri.org> wrote:
Hello Nobuhiro, > As for some distribution, a mkimage command is made a package. > However, there was not manual of mkimage. This provides manual of > mkimage. I recall looking for one several years ago ;) > +.SH SYNOPSIS > +.B mkimage > +.RB [\fIoptions\fP] mkimage -h shows more invocation variants than "mkimage [OPTIONS]": mkimage -l IMAGE mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d DATAFILE[:DATAFILE...] IMAGE ..suggesting certain OPTIONS are not [optional]. > +.SH "DESCRIPTION" > +.B mkimage > +can also be used to create images for use with U-Boot, either s/can also be/is used to/ ? > +.BI "\-l [" "uimage file name" "]" > +mkimage lists the information contained in the header of an existing U-Boot > image. s/mkimage lists/list/ > +.BI "\-A [" "architecture" "]" > +Set architecture. Pass -h as the architecture to see the list of supported > architectures. Set target architecture. If architecture is invalid, mkimage will list target architectures it supports. > +.BI "\-O [" "os" "]" > +Set operating system. bootm command of u-boot changes boot method by os type. > +Pass -h as the OS to see the list of supported OS. -O and the rest could use the same kind of fix as above - mkimage doesn't specifically check for "-O -h". also, an example would be nice if possible :) Thanks, Kim _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot