Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: is INITRAMFS_TASK still useful, or can it be tossed?
Date: Tue, 26 Aug 2014 15:56:14 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1408261555490.8552@localhost> (raw)
In-Reply-To: <CADkTA4MAOB21eT+pM7BE4nxXWm1PSOv2EPFmoLY8T2-gAu4HWA@mail.gmail.com>

On Tue, 26 Aug 2014, Bruce Ashfield wrote:

> On Tue, Aug 26, 2014 at 3:14 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> >   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"
>
> check meta-handheld, it was an existing use case we didn't want to break.

  ah, that wasn't one of the layers i had checked out, thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



      reply	other threads:[~2014-08-26 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 19:14 is INITRAMFS_TASK still useful, or can it be tossed? Robert P. J. Day
2014-08-26 19:43 ` Bruce Ashfield
2014-08-26 19:56   ` Robert P. J. Day [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.11.1408261555490.8552@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox