* Using bitbake with older kernel revisions
@ 2012-11-06 0:38 Greg Perry
2012-11-06 12:19 ` Robert Yang
0 siblings, 1 reply; 2+ messages in thread
From: Greg Perry @ 2012-11-06 0:38 UTC (permalink / raw)
To: bitbake-devel
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
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.
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.
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
[-- Attachment #2: Type: text/html, Size: 1112 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Using bitbake with older kernel revisions
2012-11-06 0:38 Using bitbake with older kernel revisions Greg Perry
@ 2012-11-06 12:19 ` Robert Yang
0 siblings, 0 replies; 2+ messages in thread
From: Robert Yang @ 2012-11-06 12:19 UTC (permalink / raw)
To: Greg Perry; +Cc: bitbake-devel
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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-11-06 12:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-06 0:38 Using bitbake with older kernel revisions Greg Perry
2012-11-06 12:19 ` Robert Yang
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.