openembedded-core.git/meta/recipes-kernel/linux/linux-yocto-dev.bb, branch 2016-10 Mirror of openembedded-core linux-yocto: Move PREFERRED_PROVIDER check to be generic 2016-09-28T09:15:54+00:00 Saul Wold sgw@linux.intel.com 2016-09-26T21:36:02+00:00 6b67018c2c0229a91fbc55c6aafb86781caf2499 This check ensures that when the PREFERRED_PROVIDER for virtual/kernel changes, the previous instances gets removed correctly so when the new instance installs files into the shared area there is not an overlap of old and new. [YOCTO #10278] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This check ensures that when the PREFERRED_PROVIDER for virtual/kernel
changes, the previous instances gets removed correctly so when the new
instance installs files into the shared area there is not an overlap of
old and new.

[YOCTO #10278]

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/4.8: add qemuarm device tree specification 2016-09-05T10:55:49+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2016-08-30T16:49:04+00:00 8c5cf8193441814e46b7e118655b4e622f785ce5 4.7+ requires a device tree for the arm versatile family of platforms. We add the definition to our 4.8 linux-yocto recipes so we can continue to boot! Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
4.7+ requires a device tree for the arm versatile family of platforms.
We add the definition to our 4.8 linux-yocto recipes so we can continue
to boot!

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-dev: bump to v4.8+ 2016-09-05T10:55:49+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2016-08-30T16:49:02+00:00 2624fc485f4c0d72ba10f2e3e0257a7fc1960807 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-dev: Ensure we don't reparse the recipe when its not being used (take 2) 2016-07-25T22:46:55+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2016-07-22T15:22:12+00:00 f1fce69766576ab62bfc5919af2af04028180950 The use of the ${AUTOREV} variable means bitbake would always re-parse the recipe. This isn't desirable when its disabled so undo the always parsing flag in this case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The use of the ${AUTOREV} variable means bitbake would always re-parse the
recipe. This isn't desirable when its disabled so undo the always parsing
flag in this case.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Revert "linux-yocto-dev: Handle performance regression" 2016-07-25T22:46:55+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2016-07-22T15:21:25+00:00 5e8cf6e568ab90365894478a272b5c28dc941031 This recipe no longer functions after this change, revert it. This reverts commit 3e0137113e894eb8b23cd43721c7ba26ff234c8f. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This recipe no longer functions after this change, revert it.

This reverts commit 3e0137113e894eb8b23cd43721c7ba26ff234c8f.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-dev: Handle performance regression 2016-07-12T22:10:02+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2016-07-08T17:00:49+00:00 5c21fd5eb8b689504e7f6a4ee2f674c32e3d928b After commit 0437a59e3c298d40aaa96af09b80bff8fcbe292d, the linux-yocto-dev recipe is being parsed every time we run "bitbake -p". This was spotted on some performance benchmarks and showed up as a performance regression. We can tweak the recipe to ensure this doesn't happen and that its only used if selected. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> 
After commit 0437a59e3c298d40aaa96af09b80bff8fcbe292d, the linux-yocto-dev
recipe is being parsed every time we run "bitbake -p". This was spotted
on some performance benchmarks and showed up as a performance regression.

We can tweak the recipe to ensure this doesn't happen and that its only
used if selected.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
linux-yocto-dev: bump to v4.6-rcX 2016-04-03T14:51:09+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2016-04-02T00:09:22+00:00 cb25dcc7c474a4f49366dbf1e6df04dd01a848dd Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto-dev: bump to 4.4-rcX 2015-12-27T11:26:58+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2015-12-18T13:28:46+00:00 30afd55016b7f3e63fdf07b0856f9bbf9be53f3d Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
linux-yocto-dev: update to 4.2-rc 2015-08-30T11:34:25+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2015-08-24T18:50:10+00:00 468fef1ccfcc5495b6d20576864269da0cdba948 The -dev kernel is now tracking 4.2 content, so we update the linux-yocto-dev recipes PV to match. (From OE-Core rev: fc22f6ee38731e60b2bc15640fa697e5af663422) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The -dev kernel is now tracking 4.2 content, so we update the
linux-yocto-dev recipes PV to match.

(From OE-Core rev: fc22f6ee38731e60b2bc15640fa697e5af663422)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto: split meta data from kernel repository 2015-07-25T13:40:57+00:00 Bruce Ashfield bruce.ashfield@windriver.com 2015-07-21T15:21:04+00:00 523e4f6a6913b64453579d27a02467e14f7df42e The linux-yocto tree has always been a combined set of kernel changes and configuration (meta) data carried in a single tree. While this format is effective at keeping kernel configuration and source modifications synchronized, it isn't always obvious to developers on how to manipulate the meta data versus the source. With this change, we remove the meta data processing from the kernel-yocto class and use the external meta-data repository that has always been used to seed the linux-yocto meta branch. After this change, linux-yocto can no longer process combined trees, and is simplified as a result. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The linux-yocto tree has always been a combined set of kernel changes
and configuration (meta) data carried in a single tree. While this
format is effective at keeping kernel configuration and source
modifications synchronized, it isn't always obvious to developers on
how to manipulate the meta data versus the source.

With this change, we remove the meta data processing from the
kernel-yocto class and use the external meta-data repository that
has always been used to seed the linux-yocto meta branch.

After this change, linux-yocto can no longer process combined trees,
and is simplified as a result.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>