From: Robert Yang <liezhi.yang@windriver.com>
To: Greg Perry <gregperry999@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Using bitbake with older kernel revisions
Date: Tue, 6 Nov 2012 20:19:06 +0800 [thread overview]
Message-ID: <5099003A.9030303@windriver.com> (raw)
In-Reply-To: <CA+ZhUHnqOTdCtXMC-y_QtdmH+Gkse80XjDgQnPqUStuBvS2A2g@mail.gmail.com>
On 11/06/2012 08:38 AM, Greg Perry wrote:
> Hello,
>
> Hopefully this is the right mailing list to ask this question, if not I
> apologize in advance and ask that you send me to the appropriate mailing
> list.
>
Hi Greg,
The right mailing list should be openembedded-core@lists.openembedded.org .
> I have a BeagleBone cross compile setup (ARM-based board), and I've
> successfully used the OE/bitbake process described at OpenEmbedded.org to
> setup of a cross compile toolchain, download source, and build an entire
> system plus software from scratch.
>
> However, the kernel revision used is several versions ahead of the patch
> branch that I want to integrate (3.2.28), as I want to integrate the
> Xenomai RTOS extensions which require kernel version 3.2.21.
>
You can set the PREFERRED_VERSION if there is already a recipe, for example,
there are the fllowing kernel recipes on the oe-core's master branch:
recipes-kernel/linux/linux-yocto_3.0.bb
recipes-kernel/linux/linux-yocto_3.2.bb
recipes-kernel/linux/linux-yocto_3.4.bb
You can look into the recipe and check the variable LINUX_VERSION for the
accurate kernel version, unfortunately, I didn't find the version (3.2.21)
which you need, the most near one is recipes-kernel/linux/linux-yocto_3.2.bb
which is 3.2.18, if this one works (just a suppose), you can set it as:
PREFERRED_VERSION_linux-yocto = "3.2"
in the .conf file, then bitbake will build linux-yocto_3.2.bb, rather than
linux-yocto_3.4.bb or linux-yocto_3.0.bb.
The setting is similar if you a 3.2.21 recipe.
// Robert
> Is it possible with OE/bitbake to specify an older kernel revision with
> accompanying system to build an older kernel and Angstrom distribution?
> Ideally I would like to regress back to the 3.2.21 kernel release and do a
> full build of that Angstrom distribution after applying the Xenomai patches
> to the 3.2.21 kernel.
>
> Thanks in advance for your help
>
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>
prev parent reply other threads:[~2012-11-06 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 0:38 Using bitbake with older kernel revisions Greg Perry
2012-11-06 12:19 ` Robert Yang [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=5099003A.9030303@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=gregperry999@gmail.com \
/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