any value in keeping INITRAMFS_TASK?
just tripped over INITRAMFS_TASK in kernel.bbclass, which claims to
be only for backward compatibility and should be replaced by INITRAMFS_IMAGE:
# NOTE: setting INITRAMFS_TASK is for backward compatibility
# The preferred method is to set INITRAMFS_IMAGE, because
# this INITRAMFS_TASK has circular dependency problems
# if the initramfs requires kernel modules
but i still see usage over in meta-openembedded/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.1[07].bb:
INITRAMFS_IMAGE = "initramfs-kexecboot-klibc-image" INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_rootfs"
should that be updated, and INITRAMFS_TASK tossed?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 26 lines · Robert P. J. Day
just tripped over
INITRAMFS_TASKin kernel.bbclass, which claims to
be only for backward compatibility and should be replaced byINITRAMFS_IMAGE:# NOTE: setting
INITRAMFS_TASKis for backward compatibility
# The preferred method is to setINITRAMFS_IMAGE, because
# thisINITRAMFS_TASKhas circular dependency problems
# if the initramfs requires kernel modulesbut i still see usage over in meta-openembedded/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.1[07].bb:
INITRAMFS_IMAGE= "initramfs-kexecboot-klibc-image"INITRAMFS_TASK= "${INITRAMFS_IMAGE}:do_rootfs"should that be updated, and
INITRAMFS_TASKtossed?rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Quoted 8 lines
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday========================================================================
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Robert,
this is is an unobvious way to allow the build in one pass of:
- a standard kernel (without initramfs)
- a second kernel embedding an initramfs
The 'preferred method' does inject the initramfs in any recipe using kernel.bbclass so to keep the old behavior (selectively add the initramfs) we can circumvent it using INITRAMFS_TASK.
So no, please, don't toss it ;)
Cheers
Andrea
Quoted 25 lines · Andrea Adami
Quoted 10 lines · Robert P. J. Day
just tripped over
INITRAMFS_TASKin kernel.bbclass, which claims to
be only for backward compatibility and should be replaced byINITRAMFS_IMAGE:# NOTE: setting
INITRAMFS_TASKis for backward compatibility
# The preferred method is to setINITRAMFS_IMAGE, because
# thisINITRAMFS_TASKhas circular dependency problems
# if the initramfs requires kernel modulesQuoted 7 lines
but i still see usage over in meta-openembedded/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.1[07].bb:
INITRAMFS_IMAGE= "initramfs-kexecboot-klibc-image"INITRAMFS_TASK= "${INITRAMFS_IMAGE}:do_rootfs"should that be updated, and
INITRAMFS_TASKtossed?Robert,
this is is an unobvious way to allow the build in one pass of:
- a standard kernel (without initramfs)
- a second kernel embedding an initramfs
Quoted 5 lines
The 'preferred method' does inject the initramfs in any recipe using kernel.bbclass so to keep the old behavior (selectively add the initramfs) we can circumvent it using
INITRAMFS_TASK.So no, please, don't toss it ;)
which is fine, but then it shouldn't be described as discouraged or
only for backward compatibility. and perhaps it should be listed in the YP reference manual in the variable glossary as well.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================