summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual/kernel-how-to.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-01-26 17:09:42 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-08 12:07:45 -0800
commitb94e91043d126b9e5669cef551e280efccd299ea (patch)
tree6478b52d7f9c34f12081e43db236e08b95b51f21 /documentation/kernel-manual/kernel-how-to.xml
parent8f9dc14e28a2adac6bd1389c1ef1f9b17ce5fa41 (diff)
downloadpoky-b94e91043d126b9e5669cef551e280efccd299ea.tar.gz
documentation/kernel-manual/kernel-how-to.xml: edits to tree construction
I made some clarifying edits to the section that describes how the YP team constructs the kernel repositories (the tree). There were some things that just weren't clear. (From yocto-docs rev: 127f0c8c89ec9b926a4ff348acc39a73f41e6fe7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-manual/kernel-how-to.xml')
-rw-r--r--documentation/kernel-manual/kernel-how-to.xml29
1 files changed, 19 insertions, 10 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index e7fa93d4cc..c43af60d36 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -54,15 +54,22 @@
54 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#local-kernel-files'>Linux Yocto Kernel</ulink>" bulleted item in The Yocto Project Development Manual. 54 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#local-kernel-files'>Linux Yocto Kernel</ulink>" bulleted item in The Yocto Project Development Manual.
55 </para> 55 </para>
56 <para> 56 <para>
57 Once the Git repository is set up on your local machine, you can switch to the 57 Once you have cloned the kernel Git repository on your local machine, you can
58 <filename>meta</filename> branch within the repository. 58 switch to the <filename>meta</filename> branch within the repository.
59 Here, you can see a snapshot of all the kernel configuration and feature descriptions that are 59 Here is an example that assumes the local Git repository for the kernel is in
60 used to build the kernel repository. 60 a top-level directory named <filename>linux-yocto-3.0</filename>:
61 <literallayout class='monospaced'>
62 $ cd ~/linux-yocto-3.0
63 $ git checkout -b meta origin/meta
64 </literallayout>
65 Once you have checked out and switched to the <filename>meta</filename> branch,
66 you can see a snapshot of all the kernel configuration and feature descriptions that are
67 used to build that particular kernel repository.
61 These descriptions are in the form of <filename>.scc</filename> files. 68 These descriptions are in the form of <filename>.scc</filename> files.
62 </para> 69 </para>
63 <para> 70 <para>
64 You should realize, however, that browsing your local snapshot of feature 71 You should realize, however, that browsing your local kernel repository
65 descriptions and patches is not an effective way to determine what is in a 72 for feature descriptions and patches is not an effective way to determine what is in a
66 particular kernel branch. 73 particular kernel branch.
67 Instead, you should use Git directly to discover the changes in a branch. 74 Instead, you should use Git directly to discover the changes in a branch.
68 Using Git is an efficient and flexible way to inspect changes to the kernel. 75 Using Git is an efficient and flexible way to inspect changes to the kernel.
@@ -76,10 +83,12 @@
76 </note> 83 </note>
77 </para> 84 </para>
78 <para> 85 <para>
79 The following steps describe what happens when the Yocto kernel team constructs 86 The following steps describe what happens when the Yocto Project Team constructs
80 the kernel tree given the introduction of a new top-level kernel feature or BSP. 87 the Yocto Linux kernel source Git repository (or tree) found at
81 These are the actions that effectively create the tree that includes the new feature, patch, 88 <ulink url='http://git.yoctoproject.org/cgit.cgi'></ulink> given the
82 or BSP: 89 introduction of a new top-level kernel feature or BSP.
90 These are the actions that effectively create the tree
91 that includes the new feature, patch or BSP:
83 <orderedlist> 92 <orderedlist>
84 <listitem><para>A top-level kernel feature is passed to the kernel build subsystem. 93 <listitem><para>A top-level kernel feature is passed to the kernel build subsystem.
85 Normally, this feature is a BSP for a particular kernel type.</para></listitem> 94 Normally, this feature is a BSP for a particular kernel type.</para></listitem>