Patchwork [10/13] linux-yocto/3.14: introduce versioned recipes

login
register
mail settings
Submitter Bruce Ashfield
Date March 27, 2014, 6:25 p.m.
Message ID <a047b35664364fc8577f758f70cd781b9d675bb1.1395944068.git.bruce.ashfield@windriver.com>
Download mbox | patch
Permalink /patch/69461/
State New
Headers show

Comments

Bruce Ashfield - March 27, 2014, 6:25 p.m.
The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
the versioned recipes here.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
 meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
 2 files changed, 58 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
Richard Purdie - March 28, 2014, 9:45 a.m.
On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
> the versioned recipes here.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
>  meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
>  2 files changed, 58 insertions(+)
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>  create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
> 
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> new file mode 100644
> index 000000000000..8faa9584acf0
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> @@ -0,0 +1,21 @@
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +KBRANCH = "standard/tiny/base"
> +LINUX_KERNEL_TYPE = "tiny"
> +KCONFIG_MODE = "--allnoconfig"
> +
> +LINUX_VERSION ?= "3.14-rc8"
> +
> +KMETA = "meta"
> +
> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"

I'm afraid we can't do this in such a simple way. The big issue is that
according to our version comparison functions (in bitbake and in the
package managers), "3.14-rc8" > "3.14". This will then break updates
from package feeds.

The traditional way we've worked around this in times gone by is the
rather ugly:

PV = "3.13+3.14-rc8+git${SRCPV}"

since in this case "3.14" > "3.13+3.14-rc8"

The better way to handle this would be "3.14~rc8" however not all of our
package backends have support for "~" at this point so we can't do that.
There is a long standing bug open about this.

The same issue also applies to the libc-headers recipe.

Cheers,

Richard
Bruce Ashfield - March 28, 2014, 12:52 p.m.
On 14-03-28 05:45 AM, Richard Purdie wrote:
> On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
>> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
>> the versioned recipes here.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
>>   meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
>>   2 files changed, 58 insertions(+)
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>> new file mode 100644
>> index 000000000000..8faa9584acf0
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>> @@ -0,0 +1,21 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH = "standard/tiny/base"
>> +LINUX_KERNEL_TYPE = "tiny"
>> +KCONFIG_MODE = "--allnoconfig"
>> +
>> +LINUX_VERSION ?= "3.14-rc8"
>> +
>> +KMETA = "meta"
>> +
>> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
>> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>
> I'm afraid we can't do this in such a simple way. The big issue is that
> according to our version comparison functions (in bitbake and in the
> package managers), "3.14-rc8" > "3.14". This will then break updates
> from package feeds.
>
> The traditional way we've worked around this in times gone by is the
> rather ugly:
>
> PV = "3.13+3.14-rc8+git${SRCPV}"
>
> since in this case "3.14" > "3.13+3.14-rc8"
>
> The better way to handle this would be "3.14~rc8" however not all of our
> package backends have support for "~" at this point so we can't do that.
> There is a long standing bug open about this.
>
> The same issue also applies to the libc-headers recipe.

eeee. Since I don't do package feeds, it's never been a problem for me.

Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away
with the PR sever as well ?

I can muck with PV, or we can hold until Linus releases over the
weekend, and I go with the released PVs.

What's your preference ?

Bruce

>
> Cheers,
>
> Richard
>
>
Martin Jansa - March 28, 2014, 1:05 p.m.
On Fri, Mar 28, 2014 at 08:52:15AM -0400, Bruce Ashfield wrote:
> On 14-03-28 05:45 AM, Richard Purdie wrote:
> > On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
> >> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
> >> the versioned recipes here.
> >>
> >> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> >> ---
> >>   meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
> >>   meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
> >>   2 files changed, 58 insertions(+)
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
> >>
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >> new file mode 100644
> >> index 000000000000..8faa9584acf0
> >> --- /dev/null
> >> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >> @@ -0,0 +1,21 @@
> >> +require recipes-kernel/linux/linux-yocto.inc
> >> +
> >> +KBRANCH = "standard/tiny/base"
> >> +LINUX_KERNEL_TYPE = "tiny"
> >> +KCONFIG_MODE = "--allnoconfig"
> >> +
> >> +LINUX_VERSION ?= "3.14-rc8"
> >> +
> >> +KMETA = "meta"
> >> +
> >> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
> >> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
> >> +
> >> +PV = "${LINUX_VERSION}+git${SRCPV}"
> >
> > I'm afraid we can't do this in such a simple way. The big issue is that
> > according to our version comparison functions (in bitbake and in the
> > package managers), "3.14-rc8" > "3.14". This will then break updates
> > from package feeds.
> >
> > The traditional way we've worked around this in times gone by is the
> > rather ugly:
> >
> > PV = "3.13+3.14-rc8+git${SRCPV}"
> >
> > since in this case "3.14" > "3.13+3.14-rc8"
> >
> > The better way to handle this would be "3.14~rc8" however not all of our
> > package backends have support for "~" at this point so we can't do that.
> > There is a long standing bug open about this.
> >
> > The same issue also applies to the libc-headers recipe.
> 
> eeee. Since I don't do package feeds, it's never been a problem for me.
> 
> Wouldn't PE bump when I go to 3.14 work as well ?

yes, but we were trying to use PE bumps only in cases where it's really
needed, using sortable PV as RP suggested is IMHO better

> Or does that go away with the PR sever as well ?

no, sewer wont help

> I can muck with PV, or we can hold until Linus releases over the
> weekend, and I go with the released PVs.
> 
> What's your preference ?
> 
> Bruce
> 
> >
> > Cheers,
> >
> > Richard
> >
> >
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
Richard Purdie - March 28, 2014, 1:32 p.m.
On Fri, 2014-03-28 at 08:52 -0400, Bruce Ashfield wrote:
> On 14-03-28 05:45 AM, Richard Purdie wrote:
> > On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
> >> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
> >> the versioned recipes here.
> >>
> >> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> >> ---
> >>   meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
> >>   meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
> >>   2 files changed, 58 insertions(+)
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
> >>
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >> new file mode 100644
> >> index 000000000000..8faa9584acf0
> >> --- /dev/null
> >> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
> >> @@ -0,0 +1,21 @@
> >> +require recipes-kernel/linux/linux-yocto.inc
> >> +
> >> +KBRANCH = "standard/tiny/base"
> >> +LINUX_KERNEL_TYPE = "tiny"
> >> +KCONFIG_MODE = "--allnoconfig"
> >> +
> >> +LINUX_VERSION ?= "3.14-rc8"
> >> +
> >> +KMETA = "meta"
> >> +
> >> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
> >> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
> >> +
> >> +PV = "${LINUX_VERSION}+git${SRCPV}"
> >
> > I'm afraid we can't do this in such a simple way. The big issue is that
> > according to our version comparison functions (in bitbake and in the
> > package managers), "3.14-rc8" > "3.14". This will then break updates
> > from package feeds.
> >
> > The traditional way we've worked around this in times gone by is the
> > rather ugly:
> >
> > PV = "3.13+3.14-rc8+git${SRCPV}"
> >
> > since in this case "3.14" > "3.13+3.14-rc8"
> >
> > The better way to handle this would be "3.14~rc8" however not all of our
> > package backends have support for "~" at this point so we can't do that.
> > There is a long standing bug open about this.
> >
> > The same issue also applies to the libc-headers recipe.
> 
> eeee. Since I don't do package feeds, it's never been a problem for me.
> 
> Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away
> with the PR sever as well ?

A PE bump would work however we try not to use those, they're a last
resort to correct things we can't otherwise fix. The PR server doesn't
help here although in future I do hope we can teach it about PE too.

> I can muck with PV, or we can hold until Linus releases over the
> weekend, and I go with the released PVs.
> 
> What's your preference ?

Might as well wait over the weekend. If Linus does go for a rc9, we'll
need to merge a version with the modified PV though.

In the meantime I might pull this series into master-next for testing
but it will not get added to master in its current form.

Cheers,

Richard
Bruce Ashfield - March 28, 2014, 1:56 p.m.
On 14-03-28 09:32 AM, Richard Purdie wrote:
> On Fri, 2014-03-28 at 08:52 -0400, Bruce Ashfield wrote:
>> On 14-03-28 05:45 AM, Richard Purdie wrote:
>>> On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
>>>> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
>>>> the versioned recipes here.
>>>>
>>>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>>>> ---
>>>>    meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
>>>>    meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
>>>>    2 files changed, 58 insertions(+)
>>>>    create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>>    create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>>>
>>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>> new file mode 100644
>>>> index 000000000000..8faa9584acf0
>>>> --- /dev/null
>>>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>> @@ -0,0 +1,21 @@
>>>> +require recipes-kernel/linux/linux-yocto.inc
>>>> +
>>>> +KBRANCH = "standard/tiny/base"
>>>> +LINUX_KERNEL_TYPE = "tiny"
>>>> +KCONFIG_MODE = "--allnoconfig"
>>>> +
>>>> +LINUX_VERSION ?= "3.14-rc8"
>>>> +
>>>> +KMETA = "meta"
>>>> +
>>>> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
>>>> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
>>>> +
>>>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> I'm afraid we can't do this in such a simple way. The big issue is that
>>> according to our version comparison functions (in bitbake and in the
>>> package managers), "3.14-rc8" > "3.14". This will then break updates
>>> from package feeds.
>>>
>>> The traditional way we've worked around this in times gone by is the
>>> rather ugly:
>>>
>>> PV = "3.13+3.14-rc8+git${SRCPV}"
>>>
>>> since in this case "3.14" > "3.13+3.14-rc8"
>>>
>>> The better way to handle this would be "3.14~rc8" however not all of our
>>> package backends have support for "~" at this point so we can't do that.
>>> There is a long standing bug open about this.
>>>
>>> The same issue also applies to the libc-headers recipe.
>>
>> eeee. Since I don't do package feeds, it's never been a problem for me.
>>
>> Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away
>> with the PR sever as well ?
>
> A PE bump would work however we try not to use those, they're a last
> resort to correct things we can't otherwise fix. The PR server doesn't
> help here although in future I do hope we can teach it about PE too.
>
>> I can muck with PV, or we can hold until Linus releases over the
>> weekend, and I go with the released PVs.
>>
>> What's your preference ?
>
> Might as well wait over the weekend. If Linus does go for a rc9, we'll
> need to merge a version with the modified PV though.

Sounds good. I'm updating the PVs to the format you showed regardless.
Might as well take a lesson from the comments in the review for next
time, in particular since I'm going to split the versioned recipe a bit
sooner for 1.7.

Cheers,

Bruce

>
> In the meantime I might pull this series into master-next for testing
> but it will not get added to master in its current form.
>
> Cheers,
>
> Richard
>
Bruce Ashfield - March 28, 2014, 5:33 p.m.
On 14-03-28 09:32 AM, Richard Purdie wrote:
> On Fri, 2014-03-28 at 08:52 -0400, Bruce Ashfield wrote:
>> On 14-03-28 05:45 AM, Richard Purdie wrote:
>>> On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
>>>> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
>>>> the versioned recipes here.
>>>>
>>>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>>>> ---
>>>>    meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
>>>>    meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
>>>>    2 files changed, 58 insertions(+)
>>>>    create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>>    create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>>>
>>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>> new file mode 100644
>>>> index 000000000000..8faa9584acf0
>>>> --- /dev/null
>>>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>>> @@ -0,0 +1,21 @@
>>>> +require recipes-kernel/linux/linux-yocto.inc
>>>> +
>>>> +KBRANCH = "standard/tiny/base"
>>>> +LINUX_KERNEL_TYPE = "tiny"
>>>> +KCONFIG_MODE = "--allnoconfig"
>>>> +
>>>> +LINUX_VERSION ?= "3.14-rc8"
>>>> +
>>>> +KMETA = "meta"
>>>> +
>>>> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
>>>> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
>>>> +
>>>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>>>
>>> I'm afraid we can't do this in such a simple way. The big issue is that
>>> according to our version comparison functions (in bitbake and in the
>>> package managers), "3.14-rc8" > "3.14". This will then break updates
>>> from package feeds.
>>>
>>> The traditional way we've worked around this in times gone by is the
>>> rather ugly:
>>>
>>> PV = "3.13+3.14-rc8+git${SRCPV}"
>>>
>>> since in this case "3.14" > "3.13+3.14-rc8"
>>>
>>> The better way to handle this would be "3.14~rc8" however not all of our
>>> package backends have support for "~" at this point so we can't do that.
>>> There is a long standing bug open about this.
>>>
>>> The same issue also applies to the libc-headers recipe.
>>
>> eeee. Since I don't do package feeds, it's never been a problem for me.
>>
>> Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away
>> with the PR sever as well ?
>
> A PE bump would work however we try not to use those, they're a last
> resort to correct things we can't otherwise fix. The PR server doesn't
> help here although in future I do hope we can teach it about PE too.
>
>> I can muck with PV, or we can hold until Linus releases over the
>> weekend, and I go with the released PVs.
>>
>> What's your preference ?
>
> Might as well wait over the weekend. If Linus does go for a rc9, we'll
> need to merge a version with the modified PV though.
>
> In the meantime I might pull this series into master-next for testing
> but it will not get added to master in its current form.

FWIW: I just fixed the PVs of libc-headers and linux-yocto_3.14 to be the
3.13+ variety.

All other comments are also incorporated and the branches repushed.

Outside of needing to override the TC libc headers default of 3.14 (that 
I left
in, expecting the full update) in local.conf, all builds continue to
work.

Bruce

>
> Cheers,
>
> Richard
>

Patch

diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
new file mode 100644
index 000000000000..8faa9584acf0
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
@@ -0,0 +1,21 @@ 
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH = "standard/tiny/base"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+LINUX_VERSION ?= "3.14-rc8"
+
+KMETA = "meta"
+
+SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
+
+COMPATIBLE_MACHINE = "(qemux86)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.14.bb b/meta/recipes-kernel/linux/linux-yocto_3.14.bb
new file mode 100644
index 000000000000..4ef9fb5780d1
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_3.14.bb
@@ -0,0 +1,37 @@ 
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH = "standard/base"
+
+# board specific branches
+KBRANCH_qemuarm  = "standard/arm-versatile-926ejs"
+KBRANCH_qemumips = "standard/mti-malta32"
+KBRANCH_qemuppc  = "standard/qemuppc"
+KBRANCH_qemux86  = "standard/common-pc/base"
+KBRANCH_qemux86-64  = "standard/common-pc-64/base"
+KBRANCH_qemumips64 = "standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "0654f2bd12d0297df0ee103192d218cb6ec7c6fe"
+SRCREV_machine_qemumips ?= "7c62bc81b74205c6e09cca4997d28888aadbd507"
+SRCREV_machine_qemuppc ?= "1e45bd09d77a7d98abb70a473184f176ee6130aa"
+SRCREV_machine_qemux86 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_machine_qemux86-64 ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_machine_qemumips64 ?= "b7834de6840292871f930ef0bd9a057b1dd4f676"
+SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
+SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.14.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
+
+LINUX_VERSION ?= "3.14-rc8"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "meta"
+
+COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"