[U-Boot] what are valid formats for initrd image downloaded and used by "bootm"

[Robert P. J. Day]

On Fri, 8 Jul 2016, Wolfgang Denk wrote:

> Dear Robert,
>
> In message <alpine.LFD.2.20.1607080356390.9216 at localhost.localdomain> you wrote:
> >
> >   using yocto project to build artifacts to tftp down to a board for
> > "bootm" command -- what are the valid formats for the "initrd" object
> > that can be recognized by "bootm"? since YP can generate a *ton* of
> > different image types. thanks.
>
> "bootm" understands botht he (deprecated) legacy uImage format, plus
> of course the (preferred) FIT images.

  ok, and one last (admittedly a bit off-topic) followup ...
openembedded supplies a class, image_types_uboot.bbclass, that can
generate a pile of u-boot related images:

IMAGE_TYPES += "ext2.u-boot ext2.gz.u-boot ext2.bz2.u-boot
   ext2.lzma.u-boot ext3.gz.u-boot ext4.gz.u-boot cpio.gz.u-boot"

if i want an immediately usable initrd i can download and pass off to
bootm, i'm assuming i can use any of those "u-boot" suffixed image
types, like, say, "cpio.gz.u-boot," which will generate a file with a
name like "blahblah...20160708082958.rootfs.cpio.gz.u-boot".

  so more an openembedded question, but am i correct in assuming that
any of those OE "u-boot" files are usable as initrds? thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================