diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-07-02 10:19:10 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-07-03 14:55:02 +0100 |
commit | d779c83e71b7a7f18773e675bd0c785fb2e90bde (patch) | |
tree | 63570142b3096a59cc8b3ee702022f4ae1c6aa9b /documentation/dev-manual/dev-manual-model.xml | |
parent | 85673e5466804f6918be72b3b27328783b5ac5c9 (diff) | |
download | poky-d779c83e71b7a7f18773e675bd0c785fb2e90bde.tar.gz |
documentation/dev-manual: Fixed "Linux Yocto" term
Throughout the manual, the kernels that are built and available through
the Yocto Project were being referenced as a "Linux Yocto kernel."
This reference is poor. First, it placed Linux and Yocto very close
together and could upset the Linux folks. Second, a better way would
have been to say "Yocto Linux kernel." I have fixed by referring to
kernels that are available through the Yocto Project as
"Yocto Project kernels."
(From yocto-docs rev: 9b8319328cd4ab4ce3363001c9feeec585d9cab9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-model.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-model.xml | 46 |
1 files changed, 23 insertions, 23 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index a4120f84db..87e10318a7 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml | |||
@@ -214,7 +214,7 @@ | |||
214 | <title><anchor id='kernel-spot' />Modifying the Kernel</title> | 214 | <title><anchor id='kernel-spot' />Modifying the Kernel</title> |
215 | 215 | ||
216 | <para> | 216 | <para> |
217 | Kernel modification involves changing the Linux Yocto kernel, which could involve changing | 217 | Kernel modification involves changing the Yocto Project kernel, which could involve changing |
218 | configuration options as well as adding new kernel recipes. | 218 | configuration options as well as adding new kernel recipes. |
219 | Configuration changes can be added in the form of configuration fragments, while recipe | 219 | Configuration changes can be added in the form of configuration fragments, while recipe |
220 | modification comes through the kernel's <filename>recipes-kernel</filename> area | 220 | modification comes through the kernel's <filename>recipes-kernel</filename> area |
@@ -222,8 +222,8 @@ | |||
222 | </para> | 222 | </para> |
223 | 223 | ||
224 | <para> | 224 | <para> |
225 | The remainder of this section presents a high-level overview of the Linux Yocto | 225 | The remainder of this section presents a high-level overview of the Yocto Project |
226 | kernel architecture and the steps to modify the Linux Yocto kernel. | 226 | kernel architecture and the steps to modify the kernel. |
227 | For a complete discussion of the kernel, see | 227 | For a complete discussion of the kernel, see |
228 | <ulink url='&YOCTO_DOCS_KERNEL_URL;'> | 228 | <ulink url='&YOCTO_DOCS_KERNEL_URL;'> |
229 | The Yocto Project Kernel Architecture and Use Manual</ulink>. | 229 | The Yocto Project Kernel Architecture and Use Manual</ulink>. |
@@ -244,7 +244,7 @@ | |||
244 | </para> | 244 | </para> |
245 | 245 | ||
246 | <para> | 246 | <para> |
247 | You can find a web interface to the Linux Yocto kernel source repositories at | 247 | You can find a web interface to the Yocto Project kernel source repositories at |
248 | <ulink url='&YOCTO_GIT_URL;'></ulink>. | 248 | <ulink url='&YOCTO_GIT_URL;'></ulink>. |
249 | If you look at the interface, you will see to the left a grouping of | 249 | If you look at the interface, you will see to the left a grouping of |
250 | Git repositories titled "Yocto Linux Kernel." | 250 | Git repositories titled "Yocto Linux Kernel." |
@@ -252,17 +252,17 @@ | |||
252 | the Yocto Project: | 252 | the Yocto Project: |
253 | <itemizedlist> | 253 | <itemizedlist> |
254 | <listitem><para><emphasis><filename>linux-yocto-2.6.34</filename></emphasis> - The | 254 | <listitem><para><emphasis><filename>linux-yocto-2.6.34</filename></emphasis> - The |
255 | stable Linux Yocto kernel that is based on the Linux 2.6.34 release.</para></listitem> | 255 | stable Yocto Project kernel that is based on the Linux 2.6.34 released kernel.</para></listitem> |
256 | <listitem><para><emphasis><filename>linux-yocto-2.6.37</filename></emphasis> - The | 256 | <listitem><para><emphasis><filename>linux-yocto-2.6.37</filename></emphasis> - The |
257 | stable Linux Yocto kernel that is based on the Linux 2.6.37 release.</para></listitem> | 257 | stable Yocto Project kernel that is based on the Linux 2.6.37 released kernel.</para></listitem> |
258 | <listitem><para><emphasis><filename>linux-yocto-3.0</filename></emphasis> - The stable | 258 | <listitem><para><emphasis><filename>linux-yocto-3.0</filename></emphasis> - The stable |
259 | Linux Yocto kernel that is based on the Linux 3.0 release.</para></listitem> | 259 | Yocto Project kernel that is based on the Linux 3.0 released kernel.</para></listitem> |
260 | <listitem><para><emphasis><filename>linux-yocto-3.0-1.1.x</filename></emphasis> - The | 260 | <listitem><para><emphasis><filename>linux-yocto-3.0-1.1.x</filename></emphasis> - The |
261 | stable Linux Yocto kernel to use with the Yocto Project Release 1.1.x. This kernel | 261 | stable Yocto Project kernel to use with the Yocto Project Release 1.1.x. This kernel |
262 | is based on the Linux 3.0 release</para></listitem> | 262 | is based on the Linux 3.0 released kernel.</para></listitem> |
263 | <listitem><para><emphasis><filename>linux-yocto-3.2</filename></emphasis> - The | 263 | <listitem><para><emphasis><filename>linux-yocto-3.2</filename></emphasis> - The |
264 | stable Linux Yocto kernel to use with the Yocto Project Release 1.2. This kernel | 264 | stable Yocto Project kernel to use with the Yocto Project Release 1.2. This kernel |
265 | is based on the Linux 3.2 release</para></listitem> | 265 | is based on the Linux 3.2 released kernel.</para></listitem> |
266 | <listitem><para><emphasis><filename>linux-yocto-dev</filename></emphasis> - A development | 266 | <listitem><para><emphasis><filename>linux-yocto-dev</filename></emphasis> - A development |
267 | kernel based on the latest upstream release candidate available.</para></listitem> | 267 | kernel based on the latest upstream release candidate available.</para></listitem> |
268 | </itemizedlist> | 268 | </itemizedlist> |
@@ -304,8 +304,8 @@ | |||
304 | </para> | 304 | </para> |
305 | 305 | ||
306 | <note> | 306 | <note> |
307 | Keep in mind the figure does not take into account all the supported Linux Yocto | 307 | Keep in mind the figure does not take into account all the supported Yocto |
308 | kernel types, but rather shows a single generic kernel just for conceptual purposes. | 308 | Project kernel types, but rather shows a single generic kernel just for conceptual purposes. |
309 | Also keep in mind that this structure represents the Yocto Project source repositories | 309 | Also keep in mind that this structure represents the Yocto Project source repositories |
310 | that are either pulled from during the build or established on the host development system | 310 | that are either pulled from during the build or established on the host development system |
311 | prior to the build by either cloning a particular kernel's Git repository or by | 311 | prior to the build by either cloning a particular kernel's Git repository or by |
@@ -324,13 +324,13 @@ | |||
324 | 324 | ||
325 | <para> | 325 | <para> |
326 | You make kernel source code available on your host development system by using | 326 | You make kernel source code available on your host development system by using |
327 | Git to create a bare clone of the Linux Yocto kernel Git repository | 327 | Git to create a bare clone of the Yocto Project kernel Git repository |
328 | in which you are interested. | 328 | in which you are interested. |
329 | Then, you use Git again to clone a copy of that bare clone. | 329 | Then, you use Git again to clone a copy of that bare clone. |
330 | This copy represents the directory structure on your host system that is particular | 330 | This copy represents the directory structure on your host system that is particular |
331 | to the kernel you want. | 331 | to the kernel you want. |
332 | These are the files you actually modify to change the kernel. | 332 | These are the files you actually modify to change the kernel. |
333 | See the <link linkend='local-kernel-files'>Linux Yocto Kernel</link> item earlier | 333 | See the <link linkend='local-kernel-files'>Yocto Project Kernel</link> item earlier |
334 | in this manual for an example of how to set up the kernel source directory | 334 | in this manual for an example of how to set up the kernel source directory |
335 | structure on your host system. | 335 | structure on your host system. |
336 | </para> | 336 | </para> |
@@ -425,9 +425,9 @@ | |||
425 | <note>While it is certainly possible to modify the kernel without involving | 425 | <note>While it is certainly possible to modify the kernel without involving |
426 | a local Git repository, the suggested workflow for kernel modification | 426 | a local Git repository, the suggested workflow for kernel modification |
427 | using the Yocto Project does use a Git repository.</note></para></listitem> | 427 | using the Yocto Project does use a Git repository.</note></para></listitem> |
428 | <listitem><para><emphasis>Establish a local copy of the Linux Yocto kernel files on your | 428 | <listitem><para><emphasis>Establish a local copy of the Yocto Project kernel files on your |
429 | system</emphasis>: In order to make modifications to the kernel you need two things: | 429 | system</emphasis>: In order to make modifications to the kernel you need two things: |
430 | a bare clone of the Linux Yocto kernel you are modifying and | 430 | a bare clone of the Yocto Project kernel you are modifying and |
431 | a copy of that bare clone. | 431 | a copy of that bare clone. |
432 | The bare clone is required by the build process and is the area to which you | 432 | The bare clone is required by the build process and is the area to which you |
433 | push your kernel source changes (pulling does not work with bare clones). | 433 | push your kernel source changes (pulling does not work with bare clones). |
@@ -435,7 +435,7 @@ | |||
435 | source files. | 435 | source files. |
436 | You make your changes to the files in this copy of the bare clone. | 436 | You make your changes to the files in this copy of the bare clone. |
437 | For information on how to set these two items up, see the bulleted item | 437 | For information on how to set these two items up, see the bulleted item |
438 | "<link linkend='local-kernel-files'>Linux Yocto Kernel</link>" | 438 | "<link linkend='local-kernel-files'>Yocto Project Kernel</link>" |
439 | earlier in this manual.</para></listitem> | 439 | earlier in this manual.</para></listitem> |
440 | <listitem><para><emphasis>Make changes to the kernel source code if | 440 | <listitem><para><emphasis>Make changes to the kernel source code if |
441 | applicable</emphasis>: Modifying the kernel does not always mean directly | 441 | applicable</emphasis>: Modifying the kernel does not always mean directly |
@@ -506,8 +506,8 @@ | |||
506 | which allows you to distribute the layer.</para></listitem> | 506 | which allows you to distribute the layer.</para></listitem> |
507 | <listitem><para><emphasis>If applicable, share your in-tree changes</emphasis>: | 507 | <listitem><para><emphasis>If applicable, share your in-tree changes</emphasis>: |
508 | If the changes you made | 508 | If the changes you made |
509 | are suited for all Linux Yocto users, you might want to send them on for inclusion | 509 | are suited for all Yocto Project kernel users, you might want to send them on |
510 | into the Linux Yocto Git repository. | 510 | for inclusion into the upstream kernel's Git repository. |
511 | If the changes are accepted, the Yocto Project Maintainer pulls them into | 511 | If the changes are accepted, the Yocto Project Maintainer pulls them into |
512 | the master branch of the kernel tree. | 512 | the master branch of the kernel tree. |
513 | Doing so makes them available to everyone using the kernel.</para></listitem> | 513 | Doing so makes them available to everyone using the kernel.</para></listitem> |
@@ -522,7 +522,7 @@ | |||
522 | 522 | ||
523 | <para> | 523 | <para> |
524 | Application development involves creation of an application that you want to be able | 524 | Application development involves creation of an application that you want to be able |
525 | to run on your target hardware, which is running a Linux Yocto image. | 525 | to run on your target hardware, which is running a Yocto Project kernel image. |
526 | The Yocto Project provides an Application Development Toolkit (ADT) that | 526 | The Yocto Project provides an Application Development Toolkit (ADT) that |
527 | facilitates quick development and integration of your application into its run-time environment. | 527 | facilitates quick development and integration of your application into its run-time environment. |
528 | Using the ADT you can employ cross-development toolchains designed for your target hardware | 528 | Using the ADT you can employ cross-development toolchains designed for your target hardware |
@@ -567,7 +567,7 @@ | |||
567 | "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and | 567 | "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and |
568 | "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both | 568 | "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both |
569 | in the Yocto Project Quick Start for requirements.</para></listitem> | 569 | in the Yocto Project Quick Start for requirements.</para></listitem> |
570 | <listitem><para><emphasis>Secure the Linux Yocto Kernel Target Image</emphasis>: | 570 | <listitem><para><emphasis>Secure the Yocto Project Kernel Target Image</emphasis>: |
571 | You must have a target kernel image that has been built using the OpenEmbeded | 571 | You must have a target kernel image that has been built using the OpenEmbeded |
572 | build system.</para> | 572 | build system.</para> |
573 | <para>Depending on whether the Yocto Project has a pre-built image that matches your target | 573 | <para>Depending on whether the Yocto Project has a pre-built image that matches your target |
@@ -591,7 +591,7 @@ | |||
591 | See the | 591 | See the |
592 | "<link linkend='kernel-modification-workflow'>Kernel Modification Workflow</link>" | 592 | "<link linkend='kernel-modification-workflow'>Kernel Modification Workflow</link>" |
593 | section earlier in this manual for information on how to create a modified | 593 | section earlier in this manual for information on how to create a modified |
594 | Linux Yocto kernel.</para></listitem> | 594 | Yocto Project kernel.</para></listitem> |
595 | </itemizedlist></para> | 595 | </itemizedlist></para> |
596 | <para>For information on pre-built kernel image naming schemes for images | 596 | <para>For information on pre-built kernel image naming schemes for images |
597 | that can run on the QEMU emulator, see the | 597 | that can run on the QEMU emulator, see the |