linux/poky.git/meta/classes/kernel-yocto.bbclass, branch bernard-5.0-alpha

linux-yocto: streamline BSP bootstrapping

2011-02-09T11:11:07+00:00

In order to build BSPs that were not already integrated into the upstream linux yocto kernel AND keep the git fetcher happy, some fairly complex anonymous python sections were required. These sections cause problems with variable expansion and SRCREV processing. With the updated git fetcher code, we can streamline the BSP boostrapping process and drop 99% of the anonymous python code. This commit has the following changes to support BSP boot strapping and simplication for existing BSPs. - KMETA is set per-recipe rather than in python code - undefined machines are no longer used, but instead common branch names are set per-recipe - fallback machine SRCREVs are present in the default revisions file - A new variable YOCTO_KERNEL_EXTERNAL_BRANCH should be set in the local.conf for new BSPs instead of being programatically determined in the anonymous python. - No more explicity KMACHINE variable expansion and manipulation, since the tools and build phases no longer require it due to the per-recipe fallbacks. Integrated/merged BSPs are unaffected by the changes and have been regression tested. Signed-off-by: Bruce Ashfield foo Signed-off-by: Bruce Ashfield

kernel-yocto: Ensure python code has awlays run before SRCPV is expanded

2011-02-08T12:05:36+00:00

The python code in this class file needs to run before SRCPV is expanded and calls into the fetcher are made. To so this we create a python function and prepend a call to it before SRCPV's get_srcrev() call. Ugly, ugly, ugly but the ordering is guaranteed. If this doesn't happen, the fetcher can end up in two different states and there may be caching implications of this. Signed-off-by: Richard Purdie

kernel-yocto/poky-default-revisions: Ensure SRCREV_machine is set for the kernels

2011-02-08T12:05:36+00:00

If we don't do this and try to bring up a new machine we can trigger network access to resolve the branch name to a revision which is undesireable. Signed-off-by: Richard Purdie

kernel-yocto: 'standard' isn't a valid git branch name for a SRCREV, fix

2011-02-07T09:32:44+00:00

Signed-off-by: Richard Purdie

linux-yocto/linux-libc-headers-yocto: Adjust to git fetcher improvements

2011-02-02T17:19:18+00:00

Signed-off-by: Richard Purdie

linux-yocto: export kernel configuration audit to the console

2011-02-01T23:59:43+00:00

Fixes [BUGID #692] Previously the information dumped by the kernel configuration audit scripts was only placed in log files. This isn't as useful as it could be, since they are rarely checked. This change takes the output from kconf_check and explicitly displays it to the user. Signed-off-by: Bruce Ashfield

linux-yocto: allow multiple BSPs per branch

2011-01-24T22:42:55+00:00

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

linux-yocto: update validate_branches to detected invalid commit IDs

2011-01-19T19:36:27+00:00

The previous implementation of invalid commit ID checks would error early when a bad object was detected. Rather than changing to set +e for the entire routine, we'll capture the output and do an explicit check for a bad object and throw a useful error message when it is detected. Signed-off-by: Bruce Ashfield

linux-yocto: streamline new BSP creation

2011-01-19T19:36:27+00:00

By setting BOOTSTRAP to the branch that should be used for a currently undefined BSP a build can be completed and an environment for streamlining the BSP created. With the appropriate machine.conf, and a defconfig any MACHINE can be built against and inherit the configuration of the standard yocto kernel. Signed-off-by: Bruce Ashfield

kernel-yocto: pass the build directory to configme

2011-01-10T21:04:44+00:00

configme used to be able to calculate the output/build directory when branches were always -. Branch names can now be widely different and to avoid embedding complexity in the scripts it is easier to just pass ${B} from the build system down to the scripts. Signed-off-by: Bruce Ashfield