On Fri, 8 Jul 2016, Wolfgang Denk wrote:
> Dear Robert,
>
> In message you
> wrote:
> >
> > yup, i just went through most of the above, and built a
> > *cpio.gz.u-boot format ramdisk, and it works just fine, so i'm happy.
> > onward ...
>
> For now this is OK, but you might consider switching
Dear Robert,
In message you wrote:
>
> yup, i just went through most of the above, and built a
> *cpio.gz.u-boot format ramdisk, and it works just fine, so i'm happy.
> onward ...
For now this is OK, but you might consider switching to FIT images
instead. These may look more complicated init
On Fri, 8 Jul 2016, Wolfgang Denk wrote:
> Dear Robert,
>
> In message you
> wrote:
> >
> > 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 += "ex
Dear Robert,
In message you wrote:
>
> 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-bo
On Fri, 8 Jul 2016, Wolfgang Denk wrote:
> Dear Robert,
>
> In message 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
Dear Robert,
In message 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" unde
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.
rday
--
7 matches
Mail list logo
