diff options
| author | João Henrique Ferreira de Freitas <joaohf@gmail.com> | 2014-03-10 18:07:51 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-25 12:29:38 +0000 |
| commit | 2f643ad571d11cd25521fef79a51798387ad1ebf (patch) | |
| tree | 6f0920fdb16ded4aad64834fba9f1e8508c456dc /documentation/kernel-dev | |
| parent | a41113c94f1e959c15a21b1ed40c44cfcca0338f (diff) | |
| download | poky-2f643ad571d11cd25521fef79a51798387ad1ebf.tar.gz | |
kernel-dev: New step to "Generating Configuration Files" section.
Add a new step about how to use diffconfig task to create
kernel config fragments.
Scott fixed some grammar in one of the sentences after applying the
patch.
(From yocto-docs rev: 5b7ccdbf708cbeebc2d8dc91db129fb35aabdcdd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 25 |
1 files changed, 9 insertions, 16 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index a152f9fbbe..f73f981ce8 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml | |||
| @@ -342,32 +342,25 @@ | |||
| 342 | <literallayout class='monospaced'> | 342 | <literallayout class='monospaced'> |
| 343 | $ bitbake linux-yocto -c kernel_configme -f | 343 | $ bitbake linux-yocto -c kernel_configme -f |
| 344 | </literallayout></para></listitem> | 344 | </literallayout></para></listitem> |
| 345 | <listitem><para>Copy and rename the resulting | ||
| 346 | <filename>.config</filename> file (e.g. | ||
| 347 | <filename>config.orig</filename>). | ||
| 348 | </para></listitem> | ||
| 349 | <listitem><para>Run the <filename>menuconfig</filename> | 345 | <listitem><para>Run the <filename>menuconfig</filename> |
| 350 | command: | 346 | command: |
| 351 | <literallayout class='monospaced'> | 347 | <literallayout class='monospaced'> |
| 352 | $ bitbake linux-yocto -c menuconfig | 348 | $ bitbake linux-yocto -c menuconfig |
| 353 | </literallayout></para></listitem> | 349 | </literallayout></para></listitem> |
| 354 | <listitem><para>Prepare a configuration fragment based on | 350 | <listitem><para>Run the <filename>diffconfig</filename> |
| 355 | the differences between the two files. | 351 | command to prepare a configuration fragment. |
| 356 | </para></listitem> | 352 | The resulting file <filename>fragment.cfg</filename> |
| 353 | will be placed in the | ||
| 354 | <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}</filename> directory: | ||
| 355 | <literallayout class='monospaced'> | ||
| 356 | $ bitbake linux-yocto -c diffconfig | ||
| 357 | </literallayout></para></listitem> | ||
| 357 | </orderedlist> | 358 | </orderedlist> |
| 358 | </para> | 359 | </para> |
| 359 | 360 | ||
| 360 | <para> | 361 | <para> |
| 361 | Ultimately, the configuration fragment file needs to be a | 362 | The <filename>diffconfig</filename> command creates a file that is a |
| 362 | list of Linux kernel <filename>CONFIG_</filename> assignments. | 363 | list of Linux kernel <filename>CONFIG_</filename> assignments. |
| 363 | It cannot be in <filename>diff</filename> format. | ||
| 364 | Here is an example of a command that creates your | ||
| 365 | configuration fragment file. | ||
| 366 | Regardless of the exact command you use, plan on reviewing | ||
| 367 | the output as you can usually remove some of the defaults: | ||
| 368 | <literallayout class='monospaced'> | ||
| 369 | $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg | ||
| 370 | </literallayout> | ||
| 371 | See the "<link linkend='changing-the-configuration'>Changing the Configuration</link>" | 364 | See the "<link linkend='changing-the-configuration'>Changing the Configuration</link>" |
| 372 | section for information on how to use the output as a | 365 | section for information on how to use the output as a |
| 373 | configuration fragment. | 366 | configuration fragment. |
