summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/linux/linux-yocto-dev.bb
AgeCommit message (Collapse)AuthorFiles
2017-04-12linux-yocto-dev: update to v4.11+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-04kernel.bbclass: Give sanity check function an opt-out variableCalifornia Sullivan1
Having no opt-out method and adding the task to linux-yocto.inc was causing issues. For example, linux-yocto-dev would often fail because it uses AUTOREV with no way to dynamically change the PV. Add a variable to turn off the sanity check, allowing an easy opt out, and set the opt-out variable in linux-yocto-dev, fixing the issue with AUTOREV. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-03linux-yocto-dev: add virtio fragment for virtio targetsBruce Ashfield1
Other linux-yocto recipes have the virtio fragment added to qemu* targets. If you plan on booting a kernel with qemu, we need these options .. or things like the virtual disk won't be present. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-02-19linux-yocto-dev: bump to v4.10+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-07linux-yocto-dev: update to 4.9-rcXBruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-09-28linux-yocto: Move PREFERRED_PROVIDER check to be genericSaul Wold1
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>
2016-09-05linux-yocto/4.8: add qemuarm device tree specificationBruce Ashfield1
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>
2016-09-05linux-yocto-dev: bump to v4.8+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-07-25linux-yocto-dev: Ensure we don't reparse the recipe when its not being used ↵Richard Purdie1
(take 2) 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>
2016-07-25Revert "linux-yocto-dev: Handle performance regression"Richard Purdie1
This recipe no longer functions after this change, revert it. This reverts commit 3e0137113e894eb8b23cd43721c7ba26ff234c8f. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-07-12linux-yocto-dev: Handle performance regressionRichard Purdie1
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>
2016-04-03linux-yocto-dev: bump to v4.6-rcXBruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-12-27linux-yocto-dev: bump to 4.4-rcXBruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-08-30linux-yocto-dev: update to 4.2-rcBruce Ashfield1
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>
2015-07-25linux-yocto: split meta data from kernel repositoryBruce Ashfield1
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>
2015-05-03linux-yocto-dev: introduce 4.1-rc development kernelBruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-08linux-yocto-dev: update to v3.19+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-09-10linux-yocto-dev: bump to v3.17+Bruce Ashfield1
Update the -dev recipes PV to reflect that the development tree is now at v3.17-rc4. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-09-01kernel-yocto: remove KBRANCH_DEFAULTBruce Ashfield1
KBRANCH_DEFAULT is no longer used, so we can remove it from all recipes (and it won't be missed). Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-07-25linux-yocto-dev: bump to v3.16+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-05-28linux-yocto-dev: Dynamic SRCREV updateDarren Hart1
The current implementation would result in the default SRCREVs being used by the fetcher, even though the anonymous python would update them to AUTOREV. This appears to be something to do with early parsing bitbake black magic. This patch ensures the default is never assigned if we are actually building the recipe by using a function to assign it in the first place. The USE_DEFAULT* variables are removed as they are not necessary to allow for overriding the SRCREVs. The anonymous python parse check is moved closer to the top of the recipe to be a bit more logically representative of its intended purpose. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-28linux-yocto-dev: bump to v3.14-rc4Bruce Ashfield1
Updating the version of linux-yocto-dev to reflect the integration of the 3.14-rc4 kernel. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-17linux-yocto-dev: bump version to 3.13+Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-14linux-yocto-dev: allow static SRCREVs via includeBruce Ashfield1
The linux-yocto dev recipe is intended to track the latest revisions of the kernel tree by default. To control revision churn, and integrate into a regular build schedule having the ability to specify a set of SRCREVs without modifying the recipe itself is desired. So we introduce an optional include file, and variables that control whether or not the static SRCREVs are used: USE_MACHINE_AUTOREV and USE_META_AUTOREV, to add this flexibility. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-10-30recipes: Remove PR = r0 from all recipesRichard Purdie1
Remove all PR = "r0" from all .bb files in oe-core. This was done with the command sed -e '/^PR.*=.*r0\"/d' recipes*/*/*.bb -i We've switching to the PR server, PR bumps are no longer needed and this saves people either accidentally bumping them or forgetting to remove the lines (r0 is the default anyway). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-30remove the unnecessary protocol parametersJackie Huang1
It's not necessary to specify the protocol parameter when it's the default protocol for the fetcher, e.g. the default protocol for git fetcher it git, "protocol=git" isn't needed. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-27linux-yocto-dev: bump version to 3.10+Bruce Ashfield1
The linux-yocto-dev kernel is at 3.10-rcX, so we should bump the version to reflect reality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-16linux-yocto: add qemumips64 compatibilityBruce Ashfield1
The 3.8 and linux-yocto-dev kernel trees carry qemumips64 support. Adding the board to the compatibility directly in the recipes is the first step to adding mips64 support to the broader set of packages. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-02-06linux-yocto/dev: linux-yocto development tree tracking recipeBruce Ashfield1
The linux-yocto-dev recipe uses the upstream tracking linux-yocto-dev repository. Since this tree is frequently updated, and periodically rebuilt, AUTOREV is used to track its contents. This recipe is just like other linux-yocto variants, with the only difference being that to avoid network access during initial parsing, static SRCREVs are provided and overridden if the preferred kernel provider is linux-yocto-dev. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 23:00:45 +0000