Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Re: kernel versions
Date: Mon, 21 Feb 2011 08:59:51 -0700	[thread overview]
Message-ID: <4D628BF7.40503@mlbassoc.com> (raw)
In-Reply-To: <4D628A56.6020002@mlbassoc.com>

On 02/21/2011 08:52 AM, Gary Thomas wrote:
> I have my own kernel recipes (historical reasons...) which I
> now have 2 versions of. Some platforms have not yet been
> ported to the latest version and I need to keep using the
> older one for those platforms until the porting is complete.
>
> Sadly, I can't get this to work.
>
> Here's what I have
> $ tree meta-amltd/packages/linux/
> meta-amltd/packages/linux/
> ├── linux-am_2.6.32.bb
> ├── linux-am_2.6.37.bb

For clarity, this is my distribution which is layered on Poky

> $ tree meta-cobra3530p60/packages/linux/
> meta-cobra3530p60/packages/linux/
> ├── linux-am-2.6.32
> │ └── cobra3530p60
> │ ├── cobra3530p60.patch
> │ └── defconfig
> ├── linux-am_2.6.32.bbappend

This is one of my platform/machine layers

>
> I tried these settings in my machine/cobra3530p60
> PREFERRED_PROVIDER_virtual/kernel = "linux-am"
> PREFERRED_VERSION_virtual/kernel = "2.6.32"
>
> However, it still wants to build version 2.6.37
>
> What am I missing? How can I force it to use the 2.6.32 version
> for this machine?
>
> Thanks
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-02-21 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 15:52 kernel versions Gary Thomas
2011-02-21 15:59 ` Gary Thomas [this message]
2011-02-21 17:41 ` Richard Purdie
2011-02-21 18:31   ` Gary Thomas
2011-02-21 23:16     ` Richard Purdie
2011-02-23 15:20       ` Gary Thomas

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=4D628BF7.40503@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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