All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Knopper <yocto@knopper.net>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: Yocto Mailinglist <yocto@yoctoproject.org>
Subject: Re: Selecting different kernel inside an image recipe
Date: Wed, 8 Jul 2015 18:36:05 +0200	[thread overview]
Message-ID: <20150708163604.GQ5636@knopper.net> (raw)
In-Reply-To: <559D445A.4010308@linux.intel.com>

Hello Leonardo,

On Wed, Jul 08, 2015 at 10:40:10AM -0500, Leonardo Sandoval wrote:
> On 07/08/2015 09:50 AM, Klaus Knopper wrote:
> >Hello list,
> >
> >I'm trying to build variantions/brands of an image that only differ in
> >kernel configuration and kernel modules included, but everything else stays
> >the same, for the exact same board, as in the main image.
> >
> >Setting PREFERRED_PROVIDER_virtual/kernel = "different_kernel"
> >right inside in the new image recipe does not have any effect, as that
> >variable seems to be evaluated exclusively in the local.conf machine
> >file, which is read by all recipes.
> 
> This variable is commonly used inside configuration metadata (machine or
> distro conf files). You may try it there.

Please help me to understand your answer: You are saying that I do have
to change the machine or distro config used for ALL recipes, to be able
to use a different kernel configuration in ONE recipe, right?

I was really trying to avoid that. :-(

So it is really not possible to just select a different kernel config
within a normal recipe without changing the global configuration?

Regards
-Klaus


  reply	other threads:[~2015-07-08 16:35 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 [this message]
2015-07-08 17:30     ` Bruce Ashfield
2015-08-04  4:15       ` Klaus Knopper
2015-08-04 13:29         ` Trevor Woerner
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=20150708163604.GQ5636@knopper.net \
    --to=yocto@knopper.net \
    --cc=leonardo.sandoval.gonzalez@linux.intel.com \
    --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.