From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp486.redcondor.net (smtp486.redcondor.net [208.80.204.86]) by mail.openembedded.org (Postfix) with ESMTP id 95E92710CF for ; Tue, 26 Aug 2014 19:15:07 +0000 (UTC) Received: from astoria.ccjclearline.com ([64.235.106.9]) by smtp486.redcondor.net ({6695537a-536a-45f9-a249-877c85428649}) via TCP (outbound) with ESMTPS id 20140826191507380 for ; Tue, 26 Aug 2014 19:15:07 +0000 X-RC-FROM: X-RC-RCPT: Received: from [99.240.204.5] (port=54323 helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1XMMCr-0006Oe-Fe for openembedded-core@lists.openembedded.org; Tue, 26 Aug 2014 15:15:01 -0400 Date: Tue, 26 Aug 2014 15:14:58 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost To: OE Core mailing list Message-ID: User-Agent: Alpine 2.11 (LFD 23 2013-08-11) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - lists.openembedded.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: X-MAG-OUTBOUND: ccj.redcondor.net@64.235.106.9/32 Subject: is INITRAMFS_TASK still useful, or can it be tossed? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 19:15:09 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII just noticed the following -- here's snippets from kernel.bbclass: ... snip ... INITRAMFS_TASK ?= "" ... snip ... # 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 image_task = d.getVar('INITRAMFS_TASK', True) if image_task: d.appendVarFlag('do_configure', 'depends', ' ${INITRAMFS_TASK}') ... snip ... if [ "$use_alternate_initrd" = "" ] && [ "${INITRAMFS_TASK}" != "" ] ; then # The old style way of copying an prebuilt image and building it # is turned on via INTIRAMFS_TASK != "" ... snip ... i have about a dozen layers checked out and the only other place i see that variable used is: meta-oe/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.10.bb: INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_rootfs" so has INITRAMFS_TASK been obsoleted by INITRAMFS_IMAGE? or is it still worth hanging onto? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================