>Michal Panczyk wrote: >> I don't know what is the problem with SD images but I know that you >> won't boot off the flash just like that. There were some changes in >> kernel configuration and no the labrun file is a must to boot. Check >> at http://bugs.openembedded.org/show_bug.cgi?id=3920 for details. >> BTW Does any one know smart idea how to add a labrun to jffs2 images >> (and just for jffs2 images!) for h2200 ? A description of the idea >> would be enough - I can try to make a patch for OE. > >You could try something like IMAGE_POSTPROCESS_COMMAND_jffs2 = >"<something>", but I'm not sure how that interacts with multiple image >formats. > >regards, > >Koen
I think this is not something we want. labrun should only exist on jffs2 image, otherwise when trying to boot off SD LAB will find labrun telling it to boot off internal flash (I guess - newer tested this combination myself). IMAGE_POSTPROCESS_COMMAND_jffs2 would produce labrun in /boot and leave it there for rest of images (at least that's how I understand bitbaking process - until explicitly told to change to whole image the rootfs dir is untouched/not regenerated). How about redefining IMAGE_CMD_jffs2 to 3 commands : 1) adding labrun to rootfs 2) generating rootfs 3) removing labrun from rootfs Or ... Maybe it labrun should be left as a part of history and it should be handled by initramfs commands ? I am sorry - I had bad experience on initramfs bootmenu image for h5000 due to bootldr leaving garbage in command line. I remember you having more luck with h2200. Koen, what do you thing about it ? -- Michal Panczyk _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
