linux/poky.git/meta/classes/kernel-yocto.bbclass, branch yocto-3.3.5

kernel-yocto: Simplify no git repo case in do_kernel_checkout

2021-09-09T09:19:42+00:00

If the kernel sources are not fetched via git, a local git repository is created in do_kernel_checkout. In this case we know that there will be no remote branches and we will already be on the correct branch (since only one branch will exist). So we can simplify things by skipping these steps. This also removes the assumption that the default git branch name will be "master". Prior to this change, the final git checkout command in do_kernel_checkout could fail if a local git repo was created and the user had changed init.defaultBranch in their gitconfig. (From OE-Core rev: 0c8d643d7b474a845588ad7dbf86f85a9aad5c49) Signed-off-by: Paul Barker Signed-off-by: Richard Purdie (cherry picked from commit af2a9c92d4498492ca23388c7b4bbed48abdc4d7) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

linux-yocto-dev: base AUTOREV on specified version

2021-07-20T18:05:45+00:00

linux-yocto-dev tracks the latest mainline kernel, and uses standard/* for that support. Archived -dev versions are under v/standard/base. This policy works, except that a released branch will still follow the new kernel versions, causing potential breakage with newer kernels than are supported in that release. Rather than lock the SRCREVs and update branches in old releases, we can preserve the AUTOREV nature of -dev, and allow them to switch automatically to the archived branch based on the LINUX_VERSION in the -dev recipe (which is unchanged in the release branch). This is consistent with the other branch switching done for the kernels and with the -dev workflow. (From OE-Core rev: b3228b4140575bfc20cb4e5bade0f3737d374e86) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit 84e14b6116a7d1e52051c5c80be2d8e3db67c2d7) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

kernel-yocto.bbclass: chdir to ${WORKDIR} for do_kernel_checkout

2021-05-04T21:57:50+00:00

It chdirs to ${S} at the beginning of task do_kernel_checkout. Then it removes ${S} when it still resides in ${S}. It may fail to run the task do_kernel_checkout when bitbake is called by third-part wrapper script. So chdir to ${WORKDIR} by default for do_kernel_checkout. And it will chdir to ${S} afterwards in task do_kernel_checkout. (From OE-Core rev: 51b03665de86c14f5b3887a60154b118c0d37aa3) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie (cherry picked from commit cf0e3397d3f86c7ea1f3c66c50a44d6205f5921b) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

kernel-yocto: fix do_kernel_configme indentation

2021-04-06T21:37:23+00:00

(From OE-Core rev: 6a2a1a0d38499b2537e1b39ac34677cd52b81fc0) Signed-off-by: Yann Dirson Signed-off-by: Richard Purdie

kernel-yocto: add KBUILD_DEFCONFIG search location to failure message

2020-09-25T09:54:30+00:00

It was pointed out that since the check for the existence of KBUILD_DEFCONFIG knows where it is looking, that should be part of the error/log message. We only look in one location for the defconfigs, so add where we checked to the message. (From OE-Core rev: 1d4d80be41d273abd1fb6416976603d924457973) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: only replace leading -I in include paths

2020-09-03T08:44:30+00:00

We just want to remove the first '-I' in $d, hence removing the g' of sed avoid changing the real path which is include '-I' We also add an anchor to the regex to only match -I at the start of the path. (From OE-Core rev: 12af8abebf0a1b8bd5689f613497f45a7778ab2d) Signed-off-by: Yanfei Xu Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: checksum all modifications to available kernel fragments directories

2020-08-28T06:08:37+00:00

This is based on the patch from Zhaolong Zhang [kernel-yocto: checksum indirect cfg and scc files] While the recommended manner to share/reuse feature fragments is to maintain them in a kernel-meta repository and track the changes via the standard SRCREV fetcher mechanism, that method is not always practical for small sets of features or for quick testing of changes. These other flows use .scc files on the SRC_URI. It has been noted that config fragments or other features indirectly included by those .scc files will not trigger the kernel meta-data to be re-run and hence a build can continue with stale data (or not be triggered at all). To solve this issue, we can collect the directories that are searchable via FILESEXTRAPATHS and add them to the do_kernel_metadata task checksum. This allows modifications, additions and removals from the potential kernel feature directories to trigger a re-execution of the meta data task. (From OE-Core rev: 09f4db415fb6a1398e9e9b359630043c833f6118) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: allow promotion of configuration warnings to errors

2020-08-28T06:08:37+00:00

It was requested to add the ability to upgrade configuration warnings to errors, so that they can't be missed in a build. Add a flag KMETA_AUDIT_WERROR, that when set, triggers a bb.fatal at the end of configuration checking if any warnings are found. This is off by default, but is available for those that want to enable it in their kernel recipe or bbappend. (From OE-Core rev: b26a6df7efdaf640c612f6d557a2e74b4dc58af3) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: split meta data gathering into patch and config phases

2020-08-13T07:07:00+00:00

do_kernel_metadata gathers and sanitizes the meta-data that is used in later steps of the kernel-yocto build process. The processing takes the form of configuration and patch gathering. The current single pass of both config and patch gathering means that patches can't modify in-tree configuration elements (although this makes tracing configuration changes harder, it is a valid workflow). We can divide the routine into a patch and configuration phase, and call the config variant after patching is done. This keeps the common parts of the gahering intact, but allows us flexibilty in when the stages happen. (From OE-Core rev: 004da4c6c6029bb2bdcea6da8afa70368ddd1bca) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: set cwd before querying the meta data dir

2020-08-13T07:07:00+00:00

To aid classifying options and streamling reports, fragments and classification info are consolidated into a kernel meta directory. The name of the meta directory is (somewhat) flexible, and hence is queried by the tools and created if it doesn't exist. The recent enhancements to the .config auditing introduced a new query for the meta directory, but isn't being run in the kernel's source directory .. and is hence creating an unwanted file in $TOPDIR. We set the kernel source directory as the cwd for the call, and everything goes back to where it belongs. (From OE-Core rev: 36f95f5e22cb4858c927f2a5a3bfeae630a41f1d) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie