summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel/kern-tools
Commit message (Collapse)AuthorAgeFilesLines
* linux-yocto: detect and avoid branch revision checking for AUTOREVBruce Ashfield2011-05-171-1/+1
| | | | | | | | | | | | | | | When a BSP or layer specifies an AUTOREV for SRCREV, the logic that matches expected vs real branch heads doesn't apply. We always want the latest. To solve the issues with invalid git revs causing validation failures, we detect the AUTOINC value and do a early return, skipping validation. (From OE-Core rev: b4f1845f7cf42059984112e3f41a323b4c9d6dfd) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: error if features are not foundBruce Ashfield2011-05-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | Fixes bug: [YOCTO #955] Updating the SRCREV to pickup the kern-tools change: [ updateme: error if features are not found Rather than silently dropping addon features, we emit a warning and then exit with a failure code. The caller can then abort a build and not simply miss features. Passing --no-strict to the script disables this new functionality if for some reason a feature description is missing on purpose. ] (From OE-Core rev: d7f3e91c15328440ffbf501c502098133fd34d3a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: error if meta data not presentBruce Ashfield2011-05-101-1/+1
| | | | | | | | | | | | | | | | | | | | There are valid reasons to build repositories without meta data present and there are times when this is an error. This change adds sanity tests to the build process to detect missing meta data and throw an informative error message. Sanity checking is only triggered from recipes (linux-yocto) that always require meta data to be present. Other recipes are not impacted and can auto-generate meta data as required. Without this change the build process suceeds, but incorrect meta data will be used (with no user knowledge), which is not the desired behaviour. (From OE-Core rev: adf9f92e2f8f6cc3deba72a194ded85e160ad9e3) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: safely process unbranched repositoriesBruce Ashfield2011-05-051-1/+1
| | | | | | | | | | | | | | The BSP bootstrap and -dev use cases can be applied against unbranched or repos without meta data. To allow the proper and safe processing of those repositories, slight modifications to the tools are required to pass the branch on the command line (rather than detecting it always) and to only checkout branches that exist. (From OE-Core rev: ae754be8b43677604a853ec6f62b2490a91d8836) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: apply meta data to external reposBruce Ashfield2011-05-051-1/+1
| | | | | | | | | | | | | | To support quick uprev and testing, it is desireable to build repositories that do not have embedded meta data. In this scenario the meta data can be automatically created or provided externally. This commit supports the first situation by detecting the lack of meta data and then automatically creating a base set of meta files. (From OE-Core rev: 32c56cd6a5756f21d19d8a32239b783a7854aed3) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-default-revisions: move the SRCREV to recipe fileYu Ke2011-05-041-0/+1
| | | | | | | | | in this case, those non poky distro can also use these recipe normally (From OE-Core rev: 0a57bd226cdb8332707fa0f46fcf0b067f03701a) Signed-off-by: Yu Ke <ke.yu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix git.pokylinux.org urls to git.yoctoproject.orgRichard Purdie2011-04-211-1/+1
| | | | | | (From OE-Core rev: adbf55721ee956897c0951cff63aeb1defb3c738) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: update to the new repositoryBruce Ashfield2011-01-251-3/+3
| | | | | | | | | | As the first of several changes to the kern-tools coupled to the branch management in the yocto kernels the repository is being renamed to it proper name. This change switches us to that newly created repo. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* linux-yocto: allow multiple BSPs per branchBruce Ashfield2011-01-241-1/+1
| | | | | | | | | | | | | | | | | | | | By default the linux-yocto recipes operate on the current branch and use it as a trigger to locate the description of a board. This model works well when using the git repo outside of a build system since the commands can be simply invoked and will do something useful. However, it does mean that you can't have two BSPs that differ only by configuration, building out of a single branch in the repository. This means that you must have many branches for very similar BSPs. This model is still preferred, but having the choice of branching strategies is better. With this change we can have multiple BSPs using a single branch with the preferred description being hinted from the build system by passing the $machine value to updateme/configme. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* createme/patchme: use kgit-checkpoint to restore meta dataBruce Ashfield2010-10-041-1/+1
| | | | | | | | | | | | Fixes [BUGID: #390] The custom de-checkpoint routines used in createme/patchme destroyed data each run. This meant that incremental and expermental work couldn't be done directly in the kernel source tree itself. Using the more robust kgit-checkpoint allows that data to be persistent (until a clean is done). Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* kern_tools: allow patching on autocreated/empty branchesBruce Ashfield2010-10-041-1/+1
| | | | | | | | | | Fixes [BUGID #388] Even if we aren't creating the branch from scratch, it is possible that it has never been patched before. So let's make sure the infrastructure for patching is always in place. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* kern-tools: add dependency on guilt-nativeKevin Tian2010-09-031-2/+2
| | | | | | Fix [BUGID #262] Signed-off-by: Kevin Tian <kevin.tian@intel.com>
* Major layout change to the packages directoryRichard Purdie2010-08-271-0/+29
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>