diff options
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-faq.rst')
-rw-r--r-- | documentation/kernel-dev/kernel-dev-faq.rst | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/documentation/kernel-dev/kernel-dev-faq.rst b/documentation/kernel-dev/kernel-dev-faq.rst new file mode 100644 index 0000000000..b852769683 --- /dev/null +++ b/documentation/kernel-dev/kernel-dev-faq.rst | |||
@@ -0,0 +1,43 @@ | |||
1 | ********************** | ||
2 | Kernel Development FAQ | ||
3 | ********************** | ||
4 | |||
5 | .. _kernel-dev-faq-section: | ||
6 | |||
7 | Common Questions and Solutions | ||
8 | ============================== | ||
9 | |||
10 | The following lists some solutions for common questions. How do I use my | ||
11 | own Linux kernel ``.config`` file? Refer to the "`Changing the | ||
12 | Configuration <#changing-the-configuration>`__" section for information. | ||
13 | How do I create configuration fragments? Refer to the "`Creating | ||
14 | Configuration Fragments <#creating-config-fragments>`__" section for | ||
15 | information. How do I use my own Linux kernel sources? Refer to the | ||
16 | "`Working With Your Own Sources <#working-with-your-own-sources>`__" | ||
17 | section for information. How do I install/not-install the kernel image | ||
18 | on the rootfs? The kernel image (e.g. ``vmlinuz``) is provided by the | ||
19 | ``kernel-image`` package. Image recipes depend on ``kernel-base``. To | ||
20 | specify whether or not the kernel image is installed in the generated | ||
21 | root filesystem, override ``RDEPENDS_kernel-base`` to include or not | ||
22 | include "kernel-image". See the "`Using .bbappend Files in Your | ||
23 | Layer <&YOCTO_DOCS_DEV_URL;#using-bbappend-files>`__" section in the | ||
24 | Yocto Project Development Tasks Manual for information on how to use an | ||
25 | append file to override metadata. How do I install a specific kernel | ||
26 | module? Linux kernel modules are packaged individually. To ensure a | ||
27 | specific kernel module is included in an image, include it in the | ||
28 | appropriate machine | ||
29 | ```RRECOMMENDS`` <&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS>`__ variable. | ||
30 | These other variables are useful for installing specific modules: | ||
31 | ```MACHINE_ESSENTIAL_EXTRA_RDEPENDS`` <&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS>`__ | ||
32 | ```MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS`` <&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS>`__ | ||
33 | ```MACHINE_EXTRA_RDEPENDS`` <&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RDEPENDS>`__ | ||
34 | ```MACHINE_EXTRA_RRECOMMENDS`` <&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RRECOMMENDS>`__ | ||
35 | For example, set the following in the ``qemux86.conf`` file to include | ||
36 | the ``ab123`` kernel modules with images built for the ``qemux86`` | ||
37 | machine: MACHINE_EXTRA_RRECOMMENDS += "kernel-module-ab123" For more | ||
38 | information, see the "`Incorporating Out-of-Tree | ||
39 | Modules <#incorporating-out-of-tree-modules>`__" section. How do I | ||
40 | change the Linux kernel command line? The Linux kernel command line is | ||
41 | typically specified in the machine config using the ``APPEND`` variable. | ||
42 | For example, you can add some helpful debug information doing the | ||
43 | following: APPEND += "printk.time=y initcall_debug debug" | ||