diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index fd0d156494..03eb5f1176 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -491,28 +491,44 @@ changing source files. However, if you have to do this, you make the changes to the files in the Build Directory. - Make kernel configuration changes - if applicable: - If your situation calls for changing the kernel's configuration, you can - use the yocto-kernel script or menuconfig - to enable and disable kernel configurations. - Using the script lets you interactively set up kernel configurations. - Using menuconfig allows you to interactively develop and test the + Make kernel configuration changes if applicable: + If your situation calls for changing the kernel's + configuration, you can use + menuconfig, + which allows you to interactively develop and test the configuration changes you are making to the kernel. - When saved, changes using menuconfig update the kernel's - .config file. - Try to resist the temptation of directly editing the .config - file found in the Build Directory at - tmp/sysroots/<machine-name>/kernel. - Doing so, can produce unexpected results when the OpenEmbedded build system - regenerates the configuration file. - Once you are satisfied with the configuration changes made using - menuconfig, you can directly compare the - .config file against a saved original and gather those - changes into a config fragment to be referenced from within the kernel's - .bbappend file. + Saving changes you make with + menuconfig updates + the kernel's .config file. + Warning + Try to resist the temptation to directly edit an + existing .config file, which is + found in the Build Directory at + tmp/sysroots/machine-name/kernel. + Doing so, can produce unexpected results when the + OpenEmbedded build system regenerates the configuration + file. + + Once you are satisfied with the configuration + changes made using menuconfig + and you have saved them, you can directly compare the + resulting .config file against an + existing original and gather those changes into a + configuration fragment file + to be referenced from within the kernel's + .bbappend file. + + Additionally, if you are working in a BSP layer + and need to modify the BSP's kernel's configuration, + you can use the + yocto-kernel + script as well as menuconfig. + The yocto-kernel script lets + you interactively set up kernel configurations. + Rebuild the kernel image with your changes: - Rebuilding the kernel image applies your changes. + Rebuilding the kernel image applies your changes. +