* McClintock Matthew-B29882 | 2013-01-14 15:14:16 [+0000]: >On Sun, Jan 13, 2013 at 11:14 PM, Suzuki K. Poulose <suzuki at in.ibm.com> wrote: >> On 01/11/2013 12:41 PM, McClintock Matthew-B29882 wrote: >>> >>> On Fri, Jan 11, 2013 at 12:42 AM, Suzuki K. Poulose <suzuki at in.ibm.com> >>> wrote: >>>> >>>> From: Suzuki K. Poulose <suzuki at in.ibm.com> >>>> >>>> Handle the RAM Disks in uImage format >>> >>> >>> As opposed to simple ext2.gz ramdisk? > >OK - it's been a while but we only supported uImage for kernel image >not ramdisk. That's what threw me off when I wrote this email I >believe. Who is "we"? Did you use kexec and pass ext2.gz as a ramdisk? u-boot supports this like for ever. You start the kernel via bootm x y z where y is the address of the ramdisk / initrd. passing the address the ext2.gz files does not work. As an alternative to this you can only pass x to bootm and the image has the "uImage.FIT" format which can contain the kernel, device tree and a ramdisk in one piece. >-M Sebastian
