linux/poky.git/meta/recipes-kernel/kern-tools, branch hardknott

meta: add explicit branch and protocol to SRC_URI

2021-11-21T11:40:35+00:00

Add branch name explicitly to SRC_URI where it's not defined and switch to using https protocol for Github projects. The change was made using convert-srcuri script in scripts/contrib. (From OE-Core rev: ab781d4e3fa7425d96ea770ddfd0f01f62018c5b) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

kern-tools: Kconfiglib: add support for bare 'modules' keyword

2021-07-06T12:02:30+00:00

Bumping the SRCREV to pickup the following for the kern-tools: commit 6dd85ff178cd76851e2184b13e545f5a88d1be30 [kconfig: change "modules" from sub-option to first-level attribute] broke parsing in 5.13+ trees. We add the new location to the parser so we can support both types of module specifications. Signed-off-by: Bruce Ashfield Without this, the kernel configuration audit for 5.13+ errors immediately. The older "option modules" parsing has been left in the code, so that older kernels continue to work as well. (From OE-Core rev: 6f15c14c3c6841589bf7fbe6ea94bf7bf9dd33a3) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit ba39e42681e7e3c6fe82686a42a9ee4b519003f9) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

kern-tools: add dropped options to audit output

2021-07-06T12:02:30+00:00

The rewrite of the configuration audit code dropped the ability to generate warnings for configuration options that didn't make it into the final .config. We integrated the following commit to restore those warnings: symbol_why: classify based on config.queue hints The config.queue has typing hints inline with each fragment, we should be using them to further classify the options, and not only relying on the special hardware.cfg, etc, files that are part of the meta data We also should be checking for options that were set to a non 'no' value, and that don't make it into the final .config, since without that check it means we are missing some warnings. (From OE-Core rev: a8edc2ddfcc1288101508eeedd9c2500e3fed296) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit f5e8a8c52386317607e333e55f710bf0393186c8) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

kern-tools: symbol-why fix and README update

2021-03-11T14:00:36+00:00

There was a bad indent in symbol_why, which we fix with a submitted patch. As part of getting that patch, it was pointed out that there's no README telling people where to send changes. So we add a basic README to avoid that in the future: 8f6aaab docs: add README for patch submission 9f1a6cb symbol_why: fix incorrect indentation of sys.exit(1) (From OE-Core rev: eea536b4368abed2248d3d0c5727a680b7368ce7) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

recipes-kernel: Add missing HOMEPAGE and DESCRIPTION for recipes.

2021-03-02T20:39:35+00:00

Fixes: [YOCTO #13471] (From OE-Core rev: 16409694f19e4d3b7bdc10a7f71c67938ce5f3ff) Signed-off-by: Ida Delphine Signed-off-by: Richard Purdie

kern-tools: non-gcc config support and option re-classification

2020-12-24T08:21:23+00:00

Integrating the following commits: 1aa9046 merge_config.sh: Translate some env variables to make variables 6fdcd64 symbol_why: allow re-classification from non-hardare to hardware With these, a non-gcc compiler can be used, since the invocation of the kernel configuration explicitly passes the variables as command line vars, versus environment variables. This means the kernel Makefile assignments are overriden and the desired compiler used. With option re-classification, we can inhibit warnings when an option has incorrectly been classified has 'hardware', and hence triggers a visible warning. [merge_config.sh: Translate some env variables to make variables] (From OE-Core rev: b5d33d13cd8618c10ae0a0379a1c8f22f6941eeb) Signed-off-by: Tyler Hicks [symbol_why: allow re-classification from non-hardare to hardware] Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: make # is not set matching more precise

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

Integrating the following commit: symbol_why: tighten 'is not set' matching Commented lines that contained CONFIG_FOO ... were being picked up as option lines and reported as invalid. We make the regex more explicit and only match on spaces before CONFIG_ to declare if a 'is not set' line is invalid. (From OE-Core rev: 63c8681e6bf763800e797f6d37f2f133abb7a0e8) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: enhance configuration queue analysis capabilities

2020-08-08T08:17:49+00:00

Enable the kernel-yocto bbclass to use enhanced capabilities from the kern-tools symbol_why.pl. We bump the kern-tools SRCREV to pickup the reworking of symbol_why, which uses Kconfiglib to provide analysis on configuration values. This is useful for debugging why a symbol specified in a fragment did not end up in the final .config. We introduce two ways to interact with the new symbol_why: 1) a replacement of the existing kconf_check script 2) a dedicated task that is explicitly invoked to dump details on the configuration. The kconf_check replacement is transparent to the user, and is run in exactly the same way as it was previously. But we get better output and more detailed diagnostics if there are symbols that don't make it into the final .config The second way to interact with symbol why is via the new task do_config_analysis. This is invoked like any other task, and by default will provide a full configuration analysis and point the user at files to look at for details. If a more targetted analysis is desired, then specific symbols can be set in the CONFIG_ANALYSIS variable. When this variable is set, the task will only run for the given symbols and provide per-variable links to the user. This variable can be set like any other, including specification in the local.conf: CONFIG_ANALYSIS_pn-linux-yocto-dev = 'NF_CONNTRACK LOCALVERSION' Which produces output as follows: WARNING: linux-yocto-dev-5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0 do_config_analysis: Configuration analysis executed, see: tmp/work/qemuarm64-poky-linux/linux-yocto-dev/5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0/NF_CONNTRACK-config-analysis.txt for details WARNING: linux-yocto-dev-5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0 do_config_analysis: Configuration audit executed, see: tmp/work/qemuarm64-poky-linux/linux-yocto-dev/5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0/NF_CONNTRACK-config-audit.txt for details WARNING: linux-yocto-dev-5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0 do_config_analysis: Configuration analysis executed, see: tmp/work/qemuarm64-poky-linux/linux-yocto-dev/5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0/LOCALVERSION-config-analysis.txt for details WARNING: linux-yocto-dev-5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0 do_config_analysis: Configuration audit executed, see: work/qemuarm64-poky-linux/linux-yocto-dev/5.8-rc++gitAUTOINC+d22beb8f8a_8fc484ed37-r0/LOCALVERSION-config-audit.txt for details (From OE-Core rev: cbc896def4c8bab3150d3405969e5dd018d62d0c) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools: fix merge_config when LD contains parameters

2020-02-08T13:20:02+00:00

To ensure that the kernel linker is used when allno/mod/yes config merge_config steps were executed, the call to make was tweaked to explicitly pass LD. But since the variable wasn't quoted, any parameters to LD (like the sysroot) were mistakenly passed to make, and hence could trigger an error on some architectures. We also tweak the logging to hightlight errors like this in the future and avoid losing it in the noise of merge configs sometimes overly verbose output. (From OE-Core rev: a60c4c116efecd7a6ee5a11b1d366bb00b9d23ce) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kern-tools-native: use more common S value and oe_runmake

2020-02-08T13:20:01+00:00

(From OE-Core rev: 83a552d0aea7f789b3a5a7ff96f3d3a5e346cc2c) Signed-off-by: Martin Jansa Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie