summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/kernel-dev')
-rw-r--r--documentation/kernel-dev/kernel-dev-advanced.xml44
1 files changed, 20 insertions, 24 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index a951aaec5d..18238c75c2 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -285,38 +285,34 @@ metadata directory. For details, see 3.3.
285 <title>Kernel Metadata Location</title> 285 <title>Kernel Metadata Location</title>
286 286
287 <para> 287 <para>
288 This metadata can be defined along with the Linux kernel 288 Kernel Metadata can be defined in either the kernel recipe
289 recipe (recipe-space) as partially described in the 289 (recipe-space) or in the kernel tree (in-tree).
290 "<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>" 290 Where you choose to define the Metadata depends on what you want
291 section as well as within the Linux kernel sources themselves 291 to do and how you intend to work.
292 (in-tree). 292 Regardless of where you define the kernel Metadata, the syntax used
293 applies equally.
293 </para> 294 </para>
294 295
295 <para> 296 <para>
296 Where you choose to store the metadata depends on what you want
297 to do and how you intend to work.
298 If you are unfamiliar with the Linux kernel and only wish 297 If you are unfamiliar with the Linux kernel and only wish
299 to apply a config and possibly a couple of patches provided to 298 to apply a configuration and possibly a couple of patches provided to
300 you by others, you may find the recipe-space mechanism to be easier 299 you by others, the recipe-space method is recommended.
301 to work with. 300 This method is also a good approach if you are working with Linux kernel
302 This is also a good approach if you are working with Linux kernel 301 sources you do not control or if you just do not want to maintain a
303 sources you do not control or if you just don't want to maintain a 302 Linux kernel Git repository on your own.
304 Linux kernel git repository on your own. 303 For partial information on how you can define kernel Metadata in
304 the recipe-space, see the
305 "<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>"
306 section.
305 </para> 307 </para>
306 308
307 <para> 309 <para>
308 If you are doing active kernel development and are already 310 Conversely, if you are actively developing a kernel and are already
309 maintaining a Linux kernel git repository of your own, you may find 311 maintaining a Linux kernel Git repository of your own, you might find
310 it more convenient to work with the metadata in the same 312 it more convenient to work with the kernel Metadata in the same
311 repository as the Linux kernel sources. 313 repository as the Linux kernel sources.
312 This can make iterative development of the Linux kernel more efficient 314 This method can make iterative development of the Linux kernel
313 outside of the BitBake environment. 315 more efficient outside of the BitBake environment.
314
315 </para>
316
317 <para>
318 Regardless of where the meta-data is stored, the syntax as
319 described in the following sections applies equally.
320 </para> 316 </para>
321 317
322 <para> 318 <para>