All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Klaus Knopper <yocto@knopper.net>,
	Yocto Mailinglist <yocto@yoctoproject.org>
Subject: Re: Selecting different kernel inside an image recipe
Date: Tue, 4 Aug 2015 09:29:45 -0400	[thread overview]
Message-ID: <55C0BE49.9020306@gmail.com> (raw)
In-Reply-To: <20150804041502.GN10184@knopper.net>

Hi Klaus,

On 08/04/15 00:15, Klaus Knopper wrote:
> So, can you confirm that it is not possible to set
> PREFERRED_PROVIDER_virtual/kernel inside an image recipe?

Confirmed, this is not possible.

I too thought it would make sense to choose one's kernel based on which
image you want to build. I was trying this a couple weeks ago and ran
into the exact same issue.

The way it was explained to me is as follows: your choice of kernel
affects a great many other "downstream" choices, therefore it needs to
be known early in the process of bitbake parsing your metadata. As a
result, there are only a few, select places where you can select your
kernel. Some of these include conf/local.conf, your distro.conf, and
your <machine>.conf. Unfortunately your <image>.conf is not one of them.

Also, if your distro or machine set the preferred kernel with an equals
sign, it is harder to override in your local.conf. In this case you
would need to try appending "_forcevariable" to your choice.

Best regards,
	Trevor


  reply	other threads:[~2015-08-04 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 14:50 Selecting different kernel inside an image recipe Klaus Knopper
2015-07-08 15:40 ` Leonardo Sandoval
2015-07-08 16:36   ` Klaus Knopper
2015-07-08 17:30     ` Bruce Ashfield
2015-08-04  4:15       ` Klaus Knopper
2015-08-04 13:29         ` Trevor Woerner [this message]
2015-08-05  7:10         ` Mike Looijmans

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=55C0BE49.9020306@gmail.com \
    --to=twoerner@gmail.com \
    --cc=yocto@knopper.net \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.