diff options
author | Dave Cobbley <david.j.cobbley@linux.intel.com> | 2018-08-14 20:05:37 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-08-23 04:26:31 +0300 |
commit | eb8dc40360f0cfef56fb6947cc817a547d6d9bc6 (patch) | |
tree | de291a73dc37168da6370e2cf16c347d1eba9df8 /poky/documentation/kernel-dev/kernel-dev-faq.xml | |
parent | 9c3cf826d853102535ead04cebc2d6023eff3032 (diff) | |
download | openbmc-eb8dc40360f0cfef56fb6947cc817a547d6d9bc6.tar.xz |
[Subtree] Removing import-layers directory
As part of the move to subtrees, need to bring all the import layers
content to the top level.
Change-Id: I4a163d10898cbc6e11c27f776f60e1a470049d8f
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'poky/documentation/kernel-dev/kernel-dev-faq.xml')
-rw-r--r-- | poky/documentation/kernel-dev/kernel-dev-faq.xml | 142 |
1 files changed, 142 insertions, 0 deletions
diff --git a/poky/documentation/kernel-dev/kernel-dev-faq.xml b/poky/documentation/kernel-dev/kernel-dev-faq.xml new file mode 100644 index 000000000..c3a20465a --- /dev/null +++ b/poky/documentation/kernel-dev/kernel-dev-faq.xml @@ -0,0 +1,142 @@ +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" +"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" +[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > + +<appendix id='kernel-dev-faq'> +<title>Kernel Development FAQ</title> + +<section id='kernel-dev-faq-section'> + <title>Common Questions and Solutions</title> + + <para> + The following lists some solutions for common questions. + + + <qandaset> + <qandaentry> + <question> + <para> + How do I use my own Linux kernel <filename>.config</filename> + file? + </para> + </question> + <answer> + <para> + Refer to the "<link linkend='changing-the-configuration'>Changing the Configuration</link>" + section for information. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How do I create configuration fragments? + </para> + </question> + <answer> + <para> + Refer to the + "<link linkend='creating-config-fragments'>Creating Configuration Fragments</link>" + section for information. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How do I use my own Linux kernel sources? + </para> + </question> + <answer> + <para> + Refer to the "<link linkend='working-with-your-own-sources'>Working With Your Own Sources</link>" + section for information. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How do I install/not-install the kernel image on the rootfs? + </para> + </question> + <answer> + <para> + The kernel image (e.g. <filename>vmlinuz</filename>) is provided + by the <filename>kernel-image</filename> package. + Image recipes depend on <filename>kernel-base</filename>. + To specify whether or not the kernel + image is installed in the generated root filesystem, override + <filename>RDEPENDS_kernel-base</filename> to include or not + include "kernel-image".</para> + <para>See the + "<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer</ulink>" + section in the Yocto Project Development Tasks Manual + for information on how to use an append file to + override metadata. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How do I install a specific kernel module? + </para> + </question> + <answer> + <para> + Linux kernel modules are packaged individually. + To ensure a specific kernel module is included in an image, + include it in the appropriate machine + <ulink url='&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS'><filename>RRECOMMENDS</filename></ulink> + variable.</para> + <para>These other variables are useful for installing specific + modules: + <literallayout class='monospaced'> + <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RDEPENDS</filename></ulink> + <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink> + <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RDEPENDS'><filename>MACHINE_EXTRA_RDEPENDS</filename></ulink> + <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RRECOMMENDS'><filename>MACHINE_EXTRA_RRECOMMENDS</filename></ulink> + </literallayout> + For example, set the following in the <filename>qemux86.conf</filename> + file to include the <filename>ab123</filename> kernel modules + with images built for the <filename>qemux86</filename> machine: + <literallayout class='monospaced'> + MACHINE_EXTRA_RRECOMMENDS += "kernel-module-ab123" + </literallayout> + For more information, see the + "<link linkend='incorporating-out-of-tree-modules'>Incorporating Out-of-Tree Modules</link>" + section. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How do I change the Linux kernel command line? + </para> + </question> + <answer> + <para> + The Linux kernel command line is typically specified in + the machine config using the <filename>APPEND</filename> variable. + For example, you can add some helpful debug information doing + the following: + <literallayout class='monospaced'> + APPEND += "printk.time=y initcall_debug debug" + </literallayout> + </para> + </answer> + </qandaentry> + </qandaset> + </para> +</section> +</appendix> +<!-- +vim: expandtab tw=80 ts=4 +--> |