sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

kernel-dev: General edits to "Kernel Metadata Location" section. 

First real pass at cleaning up the text.

(From yocto-docs rev: a550e96780b5be191a576bbb20ef28a36b20e0bc)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-01-07 14:29:13 -06:00 committed by Richard Purdie
parent ced75cec41
commit b63272cc16
1 changed files with 22 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
documentation/kernel-dev/kernel-dev-advanced.xml
View File

@ -285,38 +285,34 @@ metadata directory. For details, see 3.3.
<title>Kernel Metadata Location</title>
<para>
This metadata can be defined along with the Linux kernel
recipe (recipe-space) as partially described in the
"<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>"
section as well as within the Linux kernel sources themselves
(in-tree).
</para>
<para>
Where you choose to store the metadata depends on what you want
Kernel Metadata can be defined in either the kernel recipe
(recipe-space) or in the kernel tree (in-tree).
Where you choose to define the Metadata depends on what you want
to do and how you intend to work.
Regardless of where you define the kernel Metadata, the syntax used
applies equally.
</para>
<para>
If you are unfamiliar with the Linux kernel and only wish
to apply a config and possibly a couple of patches provided to
you by others, you may find the recipe-space mechanism to be easier
to work with.
This is also a good approach if you are working with Linux kernel
sources you do not control or if you just don't want to maintain a
Linux kernel git repository on your own.
to apply a configuration and possibly a couple of patches provided to
you by others, the recipe-space method is recommended.
This method is also a good approach if you are working with Linux kernel
sources you do not control or if you just do not want to maintain a
Linux kernel Git repository on your own.
For partial information on how you can define kernel Metadata in
the recipe-space, see the
"<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>"
section.
</para>
<para>
If you are doing active kernel development and are already
maintaining a Linux kernel git repository of your own, you may find
it more convenient to work with the metadata in the same
Conversely, if you are actively developing a kernel and are already
maintaining a Linux kernel Git repository of your own, you might find
it more convenient to work with the kernel Metadata in the same
repository as the Linux kernel sources.
This can make iterative development of the Linux kernel more efficient
outside of the BitBake environment.
</para>
<para>
Regardless of where the meta-data is stored, the syntax as
described in the following sections applies equally.
This method can make iterative development of the Linux kernel
more efficient outside of the BitBake environment.
</para>
<para>