summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev/kernel-dev-common.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-01-11 15:45:45 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-16 15:59:19 +0000
commit095ee0a7040117af3bb9d3897040150fff240119 (patch)
treeeab3697bc9c4f18fa7c55ef39e6f8493cf04b8e2 /documentation/kernel-dev/kernel-dev-common.xml
parentd5e6f2a8045346ca8c07c76b12b1a8897ba94c03 (diff)
downloadpoky-095ee0a7040117af3bb9d3897040150fff240119.tar.gz
kernel-dev: Edits to "Modifying a Recipe" section.
Edits added a couple cross-refenences back into the YP dev-manual where detailed examples of patching and configuring the kernel exist. (From yocto-docs rev: 1ae2a18f0367841d1ea9bb8d3f3d323a9b573533) 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/kernel-dev-common.xml')
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml44
1 files changed, 12 insertions, 32 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 688e12ac9a..33b834729e 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -130,6 +130,12 @@
130 detects the change in the recipe and fetches and applies the patches 130 detects the change in the recipe and fetches and applies the patches
131 before building the kernel. 131 before building the kernel.
132 </para> 132 </para>
133
134 <para>
135 For a detailed example showing how to patch the kernel, see the
136 "<ulink url='&YOCTO_DOCS_DEV_URL;#patching-the-kernel'>Patching the Kernel</ulink>"
137 section in the Yocto Project Development Manual.
138 </para>
133 </section> 139 </section>
134 140
135 <section id='changing-the-configuration'> 141 <section id='changing-the-configuration'>
@@ -156,7 +162,8 @@
156 162
157 <para> 163 <para>
158 Generally speaking, the preferred approach is to determine the 164 Generally speaking, the preferred approach is to determine the
159 incremental change you want to make and add that as a fragment. 165 incremental change you want to make and add that as a
166 configuration fragment.
160 For example, if you want to add support for a basic serial 167 For example, if you want to add support for a basic serial
161 console, create a file named <filename>8250.cfg</filename> in the 168 console, create a file named <filename>8250.cfg</filename> in the
162 <filename>${FILES}</filename> directory with the following 169 <filename>${FILES}</filename> directory with the following
@@ -182,37 +189,10 @@
182 </para> 189 </para>
183 190
184 <para> 191 <para>
185 Original Text: 192 For a detailed example showing how to configure the kernel,
186 <literallayout class='monospaced'> 193 see the
187Making wholesale or incremental changes to the Linux kernel config can be made 194 "<ulink url='&YOCTO_DOCS_DEV_URL;#configuring-the-kernel'>Configuring the Kernel</ulink>"
188by including a defconfig or configuration fragments in the SRC_URI. 195 section in the Yocto Project Development Manual.
189
190If you have a complete Linux kernel .config file you want to use, copy it as
191"defconfig" to the ${FILES} directory and add the following line to your
192linux-yocto bbappend file in your layer:
193
194 SRC_URI += "file://defconfig"
195
196Generally speaking, the preferred approach is to determine the incremental
197change you want to make and add that as a fragment. For example, if you wanted
198to add support for a basic serial console, create a file named "8250.cfg" in the
199${FILES} directory with the following content (without indentation):
200
201 CONFIG_SERIAL_8250=y
202 CONFIG_SERIAL_8250_CONSOLE=y
203 CONFIG_SERIAL_8250_PCI=y
204 CONFIG_SERIAL_8250_NR_UARTS=4
205 CONFIG_SERIAL_8250_RUNTIME_UARTS=4
206 CONFIG_SERIAL_CORE=y
207 CONFIG_SERIAL_CORE_CONSOLE=y
208
209Then include this configuration fragment in the SRC_URI:
210
211 SRC_URI += "file://8250.cfg"
212
213At the next build, bitbake will detect the change in the recipe and fetch and
214apply the new configuration before rebuilding the Linux kernel.
215 </literallayout>
216 </para> 196 </para>
217 </section> 197 </section>
218 </section> 198 </section>