mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-03-16 04:09:39 +01:00
Code Issues Packages Projects Releases Wiki Activity

kernel-dev: Formatting of the "Metadata Location" section.

Browse Source 
(From yocto-docs rev: 8ea651b8a15980421123809a1612dafe4d22ac2f)

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
2012-12-26 14:44:48 -06:00
committed by Richard Purdie
parent ea6d5be3ce
commit 7f62af0d12
1 changed files with 64 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -262,6 +262,70 @@ metadata directory. For details, see 3.3.
</para>
</section>
<section id='metadata-location'>
<title>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
to do and how you intend to work.
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.
</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
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.
</para>
<para>
Original Text:
<literallayout class='monospaced'>
This meta-data can be defined along with the Linux kernel recipe (recipe-space)
as partially described in section 2.2 as well as within the Linux kernel sources
themselves (in-tree).
Where you choose to store the meta-data depends on what you want to do and how
you intend to work. 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.
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 meta-data 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.
Regardless of where the meta-data is stored, the syntax as
described in the following sections applies equally.
</literallayout>
</para>
</section>
</chapter>
<!--
vim: expandtab tw=80 ts=4