All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>, yocto@yoctoproject.org
Subject: Re: Variable locality too restricted.
Date: Wed, 07 Dec 2011 14:10:32 +0000	[thread overview]
Message-ID: <2008188.zyrPGc484p@helios> (raw)
In-Reply-To: <752D6B50-3DE9-4257-B160-AE1CAA99F2C7@dominion.thruhere.net>

On Wednesday 07 December 2011 15:07:54 Koen Kooi wrote:
> > Changing MACHINE has other implications though; do we not have any other
> > way to switch out the kernel on a per-image basis?
> 
> And how would that work from a packaging perspective? AIUI changing
> DISTRO/MACHINE flags in an image is a recipe for failure.

I'm not suggesting changing the kernel configuration for the existing kernel; 
naturally you would need a different kernel recipe. Surely you should just be 
able to have a different kernel that is built and installed for a different 
image file? No invalidated packages necessary.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2011-12-07 14:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 13:44 Variable locality too restricted David Nyström
2011-12-07 13:52 ` Chris Larson
2011-12-07 14:05   ` Paul Eggleton
2011-12-07 14:07     ` Koen Kooi
2011-12-07 14:10       ` Paul Eggleton [this message]
2011-12-07 14:14         ` Koen Kooi
2011-12-07 14:18           ` Paul Eggleton
2011-12-08  7:24       ` David Nyström
2011-12-08 14:31         ` Bruce Ashfield
2011-12-08 18:49           ` Darren Hart
2011-12-08 22:47             ` Richard Purdie
2011-12-08 22:56               ` Darren Hart
2011-12-08 23:12                 ` Richard Purdie
2011-12-08 23:52                   ` Darren Hart
2011-12-09  8:30                     ` David Nyström
2011-12-09 18:19                       ` Darren Hart
2011-12-09 17:10               ` Trevor Woerner
2011-12-09 23:16               ` Trevor Woerner

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=2008188.zyrPGc484p@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.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.