From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert P. J. Day <rpjday@crashcourse.ca>
Date: Fri, 8 Jul 2016 09:59:44 -0400 (EDT)
Subject: [U-Boot] what are valid formats for initrd image downloaded and
 used by "bootm"
In-Reply-To: <20160708125652.05B6E100A93@atlas.denx.de>
References: <alpine.LFD.2.20.1607080356390.9216@localhost.localdomain>
 <20160708082148.A2A3F100A93@atlas.denx.de>
 <alpine.LFD.2.20.1607080453210.5437@localhost.localdomain>
 <20160708112033.789AC100A93@atlas.denx.de>
 <alpine.LFD.2.20.1607080739350.7066@localhost.localdomain>
 <20160708125652.05B6E100A93@atlas.denx.de>
Message-ID: <alpine.LFD.2.20.1607080959150.15778@localhost.localdomain>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, 8 Jul 2016, Wolfgang Denk wrote:

> Dear Robert,
>
> In message <alpine.LFD.2.20.1607080739350.7066@localhost.localdomain> 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 initially, but they are also
> much more flexible and allow for things like signed / encrypted images
> and such...

  already on my list ... in my copious free time. :-(

rday

-- 

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

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