1 files changed, 131 insertions, 0 deletions
diff --git a/documentation/kernel-dev/kernel-dev-faq.xml b/documentation/kernel-dev/kernel-dev-faq.xml
new file mode 100644
index 0000000000..7389c9c9c5
--- /dev/null
+++ b/documentation/kernel-dev/kernel-dev-faq.xml
@@ -0,0 +1,131 @@
+<!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>
+<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='generating-configuration-files'>Generating Configuration Files</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</ulink>"
+                section in the Yocto Project Development 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>
+</appendix>
+<!--
+vim: expandtab tw=80 ts=4
+-->

diff --git a/documentation/kernel-dev/kernel-dev-faq.xml b/documentation/kernel-dev/kernel-dev-faq.xml new file mode 100644 index 0000000000..7389c9c9c5 --- /dev/null +++ b/documentation/kernel-dev/kernel-dev-faq.xml
@@ -0,0 +1,131 @@
	1	<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
	2	"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
	3	[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
	4
	5	<appendix id='kernel-dev-faq'>
	6	<title>Kernel Development FAQ</title>
	7	<qandaset>
	8	<qandaentry>
	9	<question>
	10	<para>
	11	How do I use my own Linux kernel <filename>.config</filename>
	12	file?
	13	</para>
	14	</question>
	15	<answer>
	16	<para>
	17	Refer to the "<link linkend='changing-the-configuration'>Changing the Configuration</link>"
	18	section for information.
	19	</para>
	20	</answer>
	21	</qandaentry>
	22
	23	<qandaentry>
	24	<question>
	25	<para>
	26	How do I create configuration fragments?
	27	</para>
	28	</question>
	29	<answer>
	30	<para>
	31	Refer to the "<link linkend='generating-configuration-files'>Generating Configuration Files</link>"
	32	section for information.
	33	</para>
	34	</answer>
	35	</qandaentry>
	36
	37	<qandaentry>
	38	<question>
	39	<para>
	40	How do I use my own Linux kernel sources?
	41	</para>
	42	</question>
	43	<answer>
	44	<para>
	45	Refer to the "<link linkend='working-with-your-own-sources'>Working With Your Own Sources</link>"
	46	section for information.
	47	</para>
	48	</answer>
	49	</qandaentry>
	50
	51	<qandaentry>
	52	<question>
	53	<para>
	54	How do I install/not-install the kernel image on the rootfs?
	55	</para>
	56	</question>
	57	<answer>
	58	<para>
	59	The kernel image (e.g. <filename>vmlinuz</filename>) is provided
	60	by the <filename>kernel-image</filename> package.
	61	Image recipes depend on <filename>kernel-base</filename>.
	62	To specify whether or not the kernel
	63	image is installed in the generated root filesystem, override
	64	<filename>RDEPENDS_kernel-base</filename> to include or not
	65	include "kernel-image".</para>
	66	<para>See the
	67	"<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files</ulink>"
	68	section in the Yocto Project Development Manual for information on
	69	how to use an append file to override metadata.
	70	</para>
	71	</answer>
	72	</qandaentry>
	73
	74	<qandaentry>
	75	<question>
	76	<para>
	77	How do I install a specific kernel module?
	78	</para>
	79	</question>
	80	<answer>
	81	<para>
	82	Linux kernel modules are packaged individually.
	83	To ensure a specific kernel module is included in an image,
	84	include it in the appropriate machine
	85	<ulink url='&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS'><filename>RRECOMMENDS</filename></ulink>
	86	variable.</para>
	87	<para>These other variables are useful for installing specific
	88	modules:
	89	<literallayout class='monospaced'>
	90	<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RDEPENDS</filename></ulink>
	91	<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink>
	92	<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RDEPENDS'><filename>MACHINE_EXTRA_RDEPENDS</filename></ulink>
	93	<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_EXTRA_RRECOMMENDS'><filename>MACHINE_EXTRA_RRECOMMENDS</filename></ulink>
	94	</literallayout>
	95	For example, set the following in the <filename>qemux86.conf</filename>
	96	file to include the <filename>ab123</filename> kernel modules
	97	with images built for the <filename>qemux86</filename> machine:
	98	<literallayout class='monospaced'>
	99	MACHINE_EXTRA_RRECOMMENDS += "kernel-module-ab123"
	100	</literallayout>
	101	For more information, see the
	102	"<link linkend='incorporating-out-of-tree-modules'>Incorporating Out-of-Tree Modules</link>"
	103	section.
	104	</para>
	105	</answer>
	106	</qandaentry>
	107
	108	<qandaentry>
	109	<question>
	110	<para>
	111	How do I change the Linux kernel command line?
	112	</para>
	113	</question>
	114	<answer>
	115	<para>
	116	The Linux kernel command line is typically specified in
	117	the machine config using the <filename>APPEND</filename> variable.
	118	For example, you can add some helpful debug information doing
	119	the following:
	120	<literallayout class='monospaced'>
	121	APPEND += "printk.time=y initcall_debug debug"
	122	</literallayout>
	123	</para>
	124	</answer>
	125	</qandaentry>
	126
	127	</qandaset>
	128	</appendix>
	129	<!--
	130	vim: expandtab tw=80 ts=4
	131	-->