From 77a52d0b103a96d8503f5d7c65ff9e6d31dd6e89 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 26 Sep 2017 17:39:31 -0700 Subject: kernel-dev: Edits to "Fine-Tuning the Kernel Configuration File" This section needed some formatting to conform to the list structure used throughout the manual. (From yocto-docs rev: b6e6b66014963c1628c50e09787fdd46a45867b1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 65 +++++++++++++++++--------- 1 file changed, 44 insertions(+), 21 deletions(-) (limited to 'documentation/kernel-dev/kernel-dev-common.xml') diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 50e420c8d6..bfc82e2451 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -1752,28 +1752,41 @@ Fine-Tuning the Kernel Configuration File - You can make sure the .config file is as lean or efficient as - possible by reading the output of the kernel configuration fragment audit, - noting any issues, making changes to correct the issues, and then repeating. + You can make sure the .config file is as + lean or efficient as possible by reading the output of the + kernel configuration fragment audit, noting any issues, making + changes to correct the issues, and then repeating. As part of the kernel build process, the do_kernel_configcheck task runs. - This task validates the kernel configuration by checking the final - .config file against the input files. - During the check, the task produces warning messages for the following - issues: + This task validates the kernel configuration by checking the + final .config file against the input + files. + During the check, the task produces warning messages for the + following issues: - Requested options that did not make the final - .config file. - Configuration items that appear twice in the same - configuration fragment. - Configuration items tagged as "required" that were overridden. + + Requested options that did not make the final + .config file. + + + Configuration items that appear twice in the same + configuration fragment. + + + Configuration items tagged as "required" that were + overridden. + + + A board overrides a non-board specific option. + + + Listed options not valid for the kernel being + processed. + In other words, the option does not appear anywhere. - A board overrides a non-board specific option. - Listed options not valid for the kernel being processed. - In other words, the option does not appear anywhere. The do_kernel_configcheck task can @@ -1793,11 +1806,17 @@ To streamline the configuration, do the following: - Start with a full configuration that you - know works - it builds and boots successfully. - This configuration file will be your baseline. + + Use a Working Configuration: + Start with a full configuration that you + know works. + Be sure the configuration builds and boots + successfully. + Use this configuration file as your baseline. - Separately run the + + Run Configure and Check Tasks: + Separately run the do_kernel_configme and do_kernel_configcheck tasks: @@ -1805,7 +1824,9 @@ $ bitbake linux-yocto -c kernel_configcheck -f - Take the resulting list of files from the + + Process the Results: + Take the resulting list of files from the do_kernel_configcheck task warnings and do the following: @@ -1826,8 +1847,10 @@ Remove repeated and invalid options. - + + + Re-Run Configure and Check Tasks: After you have worked through the output of the kernel configuration audit, you can re-run the do_kernel_configme and -- cgit v1.2.3-54-g00ecf