summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev/kernel-dev-advanced.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-26 14:44:48 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-16 15:59:09 +0000
commit7f62af0d1207988ec54fb3dafa139f482e159825 (patch)
tree0a5f63e53ff32da507f5fee2fce274e8ae4bf168 /documentation/kernel-dev/kernel-dev-advanced.xml
parentea6d5be3ce49a6e64eb8d5fc62e72dc26cc6cb97 (diff)
downloadpoky-7f62af0d1207988ec54fb3dafa139f482e159825.tar.gz
kernel-dev: Formatting of the "Metadata Location" section.
(From yocto-docs rev: 8ea651b8a15980421123809a1612dafe4d22ac2f) 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-advanced.xml')
-rw-r--r--documentation/kernel-dev/kernel-dev-advanced.xml64
1 files changed, 64 insertions, 0 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 27c082a940..cba219fe46 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -262,6 +262,70 @@ metadata directory. For details, see 3.3.
262 </para> 262 </para>
263</section> 263</section>
264 264
265<section id='metadata-location'>
266 <title>Metadata Location</title>
267
268 <para>
269 This metadata can be defined along with the Linux kernel
270 recipe (recipe-space) as partially described in the
271 "<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>"
272 section as well as within the Linux kernel sources themselves
273 (in-tree).
274 </para>
275
276 <para>
277 Where you choose to store the metadata depends on what you want
278 to do and how you intend to work.
279 If you are unfamiliar with the Linux kernel and only wish
280 to apply a config and possibly a couple of patches provided to
281 you by others, you may find the recipe-space mechanism to be easier
282 to work with.
283 This is also a good approach if you are working with Linux kernel
284 sources you do not control or if you just don't want to maintain a
285 Linux kernel git repository on your own.
286 </para>
287
288 <para>
289 If you are doing active kernel development and are already
290 maintaining a Linux kernel git repository of your own, you may find
291 it more convenient to work with the metadata in the same
292 repository as the Linux kernel sources.
293 This can make iterative development of the Linux kernel more efficient
294 outside of the BitBake environment.
295
296 </para>
297
298 <para>
299 Regardless of where the meta-data is stored, the syntax as
300 described in the following sections applies equally.
301 </para>
302
303 <para>
304 Original Text:
305 <literallayout class='monospaced'>
306This meta-data can be defined along with the Linux kernel recipe (recipe-space)
307as partially described in section 2.2 as well as within the Linux kernel sources
308themselves (in-tree).
309
310Where you choose to store the meta-data depends on what you want to do and how
311you intend to work. If you are unfamiliar with the Linux kernel and only wish
312to apply a config and possibly a couple of patches provided to you by others,
313you may find the recipe-space mechanism to be easier to work with. This is also
314a good approach if you are working with Linux kernel sources you do not control
315or if you just don't want to maintain a Linux kernel git repository on your own.
316
317If you are doing active kernel development and are already maintaining a Linux
318kernel git repository of your own, you may find it more convenient to work with
319the meta-data in the same repository as the Linux kernel sources. This can make
320iterative development of the Linux kernel more efficient outside of the bitbake
321environment.
322
323Regardless of where the meta-data is stored, the syntax as
324described in the following sections applies equally.
325 </literallayout>
326 </para>
327</section>
328
265</chapter> 329</chapter>
266<!-- 330<!--
267vim: expandtab tw=80 ts=4 331vim: expandtab tw=80 ts=4