> -----Original Message----- > From: > linuxppc-dev-bounces+tiejun.chen=windriver....@lists.ozlabs.or > g > [mailto:linuxppc-dev-bounces+tiejun.chen=windriver....@lists.o zlabs.org] On Behalf Of Scott Wood > Sent: Wednesday, September 22, 2010 1:53 AM > To: Chen, Tiejun > Cc: ppcdev; uboot > Subject: Re: [U-Boot] cuImage and multi image? > > On Tue, 21 Sep 2010 03:03:22 +0200 > "Chen, Tiejun" <tiejun.c...@windriver.com> wrote: > > > > -----Original Message----- > > > From: Shawn Jin [mailto:shawnx...@gmail.com] > > > Sent: Tuesday, September 21, 2010 1:53 AM > > > To: Chen, Tiejun > > > Cc: ppcdev; uboot > > > Subject: Re: cuImage and multi image? > > > > > > >> I have a cuImage kernel in order to support legacy > u-boot and a > > > >> ramdisk image. Kernel boots fine if these two images are > > > separate and > > > >> "bootm $kernel $ramdisk" is used. But I can not make it to > > > work using > > > >> a single multi image that contains the kernel and ramdisk > > > images. Is > > > >> it even technically possible to boot a multi-image with cuboot > > > >> wrapper? > > > > > > > > Try the following steps: > > > > ------ > > > > 1. cp <your ramdisk.gz> arch/powerpc/boot/ramdisk.image.gz > > > > 2. make cuImage.initrd.<your target> > > > > > > > > You can get one Image, cuImage.initrd.<your target>, > > > including kernel and ramdisk. > > > > > > A follow up question. With this method, the total image size > > > (uncompressed) is limited to the 4MB (the link address of > the boot > > > wrapper)? > > > > No. > > Yes, unless you change the link address, or provide a > vmlinux_alloc callback (which currently only happens on true > OF, not cuImage). > > Unless you're talking about the "(uncompressed)"? The limit > applies to the uncompressed boot image -- anything that the > bootwrapper itself is decompressing. It does not apply to > any further uncompression of the ramdisk itself. >
He should point the latter, "the total image size", including ramdisk. But the link address should be limited for the boot Image, not for the attached ramdisk. Tiejun > -Scott > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/linuxppc-dev > _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
