diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-01-26 17:08:17 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-03-08 12:07:45 -0800 |
| commit | 8f9dc14e28a2adac6bd1389c1ef1f9b17ce5fa41 (patch) | |
| tree | e1c5f2e72d1b45dbd39347ab94d7a4c86c0c69a8 /documentation/kernel-manual/kernel-concepts.xml | |
| parent | 4baaf11e40f3baecf6b026dd17ca9878db8dc3e1 (diff) | |
| download | poky-8f9dc14e28a2adac6bd1389c1ef1f9b17ce5fa41.tar.gz | |
documentation/kernel-manual/kernel-concepts.xml: new section starting
This is the start of a new section on configuration. It is mostly
writer's notes at this point. More to be added later.
(From yocto-docs rev: db41de4ebd7040f507c5a43739f1a25d7e1d9623)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-manual/kernel-concepts.xml')
| -rw-r--r-- | documentation/kernel-manual/kernel-concepts.xml | 70 |
1 files changed, 70 insertions, 0 deletions
diff --git a/documentation/kernel-manual/kernel-concepts.xml b/documentation/kernel-manual/kernel-concepts.xml index 830042a495..922f9b312d 100644 --- a/documentation/kernel-manual/kernel-concepts.xml +++ b/documentation/kernel-manual/kernel-concepts.xml | |||
| @@ -303,6 +303,76 @@ | |||
| 303 | </section> | 303 | </section> |
| 304 | </section> | 304 | </section> |
| 305 | 305 | ||
| 306 | <section id='kernel-configuration'> | ||
| 307 | <title>Kernel Configuration</title> | ||
| 308 | <para> | ||
| 309 | Kernel configuration, along with kernel features, defines how a kernel image is | ||
| 310 | built. | ||
| 311 | Through configuration settings, you can customize a Linux Yocto kernel to be | ||
| 312 | specific to particular hardware. | ||
| 313 | For example, you can specify sound support or networking support. | ||
| 314 | This section describes basic concepts behind Kernel configuration within the | ||
| 315 | Yocto Project. | ||
| 316 | </para> | ||
| 317 | |||
| 318 | <para> | ||
| 319 | WRITER NOTES: | ||
| 320 | </para> | ||
| 321 | |||
| 322 | <para> | ||
| 323 | Explain how <filename>.config</filename> is used when the kernel image is built. | ||
| 324 | Describe the role of <filename>menuconfig</filename> regarding the | ||
| 325 | <filename>.config</filename>. | ||
| 326 | Locate the <filename>.config</filename> for the user. | ||
| 327 | Not recommended to edit the <filename>.config</filename> file directly. | ||
| 328 | You can use BitBake to build and invoke the <filename>menuconfig</filename> | ||
| 329 | tool. | ||
| 330 | </para> | ||
| 331 | |||
| 332 | <para> | ||
| 333 | Introduce the configuration fragment. | ||
| 334 | Step through the life of a configuration fragment from idea or need to | ||
| 335 | change something in the kernel to how it is used when the kernel image is built. | ||
| 336 | Describe how configuration fragments are created and where they live. | ||
| 337 | Make sure the syntax of configuration fragments is understood. | ||
| 338 | </para> | ||
| 339 | |||
| 340 | <para> | ||
| 341 | Talk in general how the user creates a configuration fragment. | ||
| 342 | Point to example B.2 of the YP Development Manual as a way to use | ||
| 343 | <filename>menuconfig</filename>. | ||
| 344 | </para> | ||
| 345 | |||
| 346 | <para> | ||
| 347 | The tool <filename>menuconfig</filename> allows you to choose the features of the | ||
| 348 | Linux Yocto kernel that will be compiled. | ||
| 349 | This tool is a convenient method to alter the <filename>.config</filename> file. | ||
| 350 | You can use a simple interface to scroll through kernel features and disable | ||
| 351 | and enable configruation variables. | ||
| 352 | When you save your changes, the contents of the <filename>.config</filename> | ||
| 353 | are altered. | ||
| 354 | You can get general information on <filename>menuconfig</filename> at | ||
| 355 | <ulink url='http://en.wikipedia.org/wiki/Menuconfig'></ulink>. | ||
| 356 | </para> | ||
| 357 | |||
| 358 | <para> | ||
| 359 | The Yocto Project employs <filename>menuconfig</filename> by invoking it through | ||
| 360 | BitBake as follows after making sure the environment setup script has been sourced: | ||
| 361 | <literallayout class='monospaced'> | ||
| 362 | $ bitbake linux-yocto -c menuconfig | ||
| 363 | </literallayout> | ||
| 364 | You can see how <filename>menuconfig</filename> is used to change a simple | ||
| 365 | kernel configuration in the | ||
| 366 | "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#changing-the-config-smp-configuration-using-menuconfig'>Changing the <filename>CONFIG_SMP</filename> | ||
| 367 | Configuration Using <filename>menuconfig</filename></ulink>" section of | ||
| 368 | The Yocto Project Development Manual. | ||
| 369 | </para> | ||
| 370 | |||
| 371 | <para> | ||
| 372 | END WRITER NOTES | ||
| 373 | </para> | ||
| 374 | </section> | ||
| 375 | |||
| 306 | <section id='kernel-tools'> | 376 | <section id='kernel-tools'> |
| 307 | <title>Kernel Tools</title> | 377 | <title>Kernel Tools</title> |
| 308 | <para> | 378 | <para> |
