On Mon, Dec 21, 2009 at 6:50 PM, Peter Tyser <ptyser@xxxxxxxxxxx> wrote: > The PowerPC architecture has the ability to embed the ramdisk located > at arch/powerpc/boot/ramdisk.image.gz into a bootable kernel image. If > the bootable kernel is in the Flattened Image Tree (FIT) format, the > ramdisk should be a node in the tree instead of being embedded directly > in the kernel executable. > > A FIT uImage with a ram filesystem can be generated using the command: > "make uImage.fit.initrd.<boardname>" where <boardname> is one of > arch/powerpc/boot/dts/<boardname>.dts. The command will generate a FIT > uImage at arch/powerpc/boot/uImage.fit.initrd.<boardname> that contains > a kernel image, device tree blob, and a ram filesystem. > > The ramdisk at arch/powerpc/boot/ramdisk.image.gz can either be an older > style "ramdisk" or a newer "ramfs" gzipped cpio archive. > > Signed-off-by: Peter Tyser <ptyser@xxxxxxxxxxx> > --- > Changes since v1: > - Don't strip leading 0x from dts ramdisk address > > arch/powerpc/boot/Makefile | 3 +++ > arch/powerpc/boot/wrapper | 20 ++++++++++++++++---- > scripts/mkits.sh | 34 ++++++++++++++++++++++++++++++++-- > 3 files changed, 51 insertions(+), 6 deletions(-) > > diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile > index e56ec21..c2a6591 100644 > --- a/arch/powerpc/boot/Makefile > +++ b/arch/powerpc/boot/Makefile > @@ -313,6 +313,9 @@ $(obj)/uImage: vmlinux $(wrapperbits) > $(obj)/uImage.fit.%: vmlinux $(obj)/%.dtb $(wrapperbits) > $(call if_changed,wrap,uboot.fit,,$(obj)/$*.dtb) > > +$(obj)/uImage.fit.initrd.%: vmlinux $(obj)/%.dtb $(wrapperbits) > + $(call if_changed,wrap,uboot.fit,,$(obj)/$*.dtb,$(obj)/ramdisk.image.gz) > + IIRC, uImage.fit.initrd.% should appear before uImage.fit.% in the Makefile so that make behaves more consistently. Speaking of which, the number of '.' in the name is getting rather large. Would you consider using 'fitImage' instead of 'uImage.fit'? g. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
