list of 2.6-related migration issues for embedded programmers?

[Robert P. J. Day]

On Mon, 19 Jul 2004, Linh Dang wrote:

> Don't use the .initramfs section option (the one that's linked with
> with vmlinux.) Build your ramdisk.image.gz as a compressed cpio
> archive. I.e. zvmlinux.initrd's .ramdisk section contains a compressed
> cpio archive instead of an compressed ext2 image.

so, just to clarify, i'm looking at arch/ppc/boot/simple/Makefile, the
excerpt:

$(obj)/zvmlinux.initrd: $(OBJS) $(LIBS) $(srctree)/$(boot)/ld.script \
                 $(images)/vmlinux.gz $(obj)/dummy.o
         $(OBJCOPY) $(OBJCOPY_ARGS) \
-->             --add-section=.ramdisk=$(images)/ramdisk.image.gz \
 		--set-section-flags=.ramdisk=contents,alloc,load,readonly,data \

and all i need to change is "ramdisk.image.gz" to, say, my "newc"
format gzipped cpio archive, "initramfs.cpio.gz", and the early kernel
code should recognize it as such automatically?

i'll give that a shot later.

rday

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/