From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Kernel 3.0.35 (fsl vs imx)
Date: Thu, 12 Dec 2013 11:08:59 -0700 [thread overview]
Message-ID: <52A9FBBB.2070400@mlbassoc.com> (raw)
In-Reply-To: <52A9D4CA.5040007@gmail.com>
On 2013-12-12 08:22, Marco wrote:
> Hello,
> if I use only the layer meta-fsl-arm I get by default the kernel linux-fsl-3.0.35-r32-14
> if I add the layers meta-fsl-arm-extra and meta-fsl-demo I get the kernel linux-imx-3.0.35-r37-14
>
> What is the suggested version to use?
These are probably the same kernel - that recipe uses INCPR which
causes the revision (-rXX) to be incremented every time the recipe
is [re]built. In your case, adding the additional layers probably
triggered the rebuild.
Note that there is only one linux-imx_3.0.35 recipe in all of
the meta-fsl* layers.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-12-12 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 15:22 Kernel 3.0.35 (fsl vs imx) Marco
2013-12-12 15:28 ` Gary Thomas
2013-12-12 17:40 ` Marco
2013-12-12 18:08 ` Gary Thomas [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=52A9FBBB.2070400@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@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.