summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-08-18 18:22:20 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-09-02 00:52:48 +0100
commit0fbba0fb46ca67e7fbb39ed9528f97d54b7fcb2b (patch)
tree8ae2162c1f81ac42ca2b4f391d995f9cd5632731
parent5865fcdf856f003cddabf476acb4e4f953db96e9 (diff)
downloadpoky-0fbba0fb46ca67e7fbb39ed9528f97d54b7fcb2b.tar.gz
kernel-dev: Updates on how to prepare for kernel modification.
WIP at this point. (From yocto-docs rev: 12e44f6ee7f9437d85c33d0789dbafe937af5664) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml26
-rw-r--r--documentation/kernel-dev/kernel-dev-intro.xml46
2 files changed, 71 insertions, 1 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 8c8fe05711..cb50912ea4 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -452,6 +452,32 @@
452 <section id="using-devtool-to-patch-the-kernel"> 452 <section id="using-devtool-to-patch-the-kernel">
453 <title>Using <filename>devtool</filename> to Patch the Kernel</title> 453 <title>Using <filename>devtool</filename> to Patch the Kernel</title>
454 454
455
456 <para role='writernotes'>
457 Some stuff here for the using devtool from the wiki.
458 This whole section is WIP.
459 <orderedlist>
460 <listitem><para role='writernotes'>
461 If you are dealing with real hardware, you can flash the
462 new kernel image to a USB stick and boot the hardware to
463 see it run.
464 </para></listitem>
465 <listitem><para role='writernotes'>
466 Checkout and modify the kernel source.
467 This is where you make your changes to the image.
468 </para></listitem>
469 <listitem><para role='writernotes'>
470 Create a new image that uses the altered kernel.
471 </para></listitem>
472 <listitem><para role='writernotes'>
473 If you are working with actual hardware, you can flash
474 the new image to a USB stick and use it to boot up the
475 hardware.
476 You can see your changes in action.
477 </para></listitem>
478 </orderedlist>
479 </para>
480
455 <para> 481 <para>
456 Patching the kernel involves changing or adding configurations to an existing kernel, 482 Patching the kernel involves changing or adding configurations to an existing kernel,
457 changing or adding recipes to the kernel that are needed to support specific hardware features, 483 changing or adding recipes to the kernel that are needed to support specific hardware features,
diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml
index 9104ed4d87..56cf6bc7e2 100644
--- a/documentation/kernel-dev/kernel-dev-intro.xml
+++ b/documentation/kernel-dev/kernel-dev-intro.xml
@@ -121,7 +121,51 @@
121 <title>Getting Ready to Develop using <filename>devtool</filename></title> 121 <title>Getting Ready to Develop using <filename>devtool</filename></title>
122 122
123 <para role='writernotes'> 123 <para role='writernotes'>
124 Need the updated wiki stuff here 124 Sections as follows:
125 <orderedlist>
126 <listitem><para role='writernotes'>
127 Source the oe-init-build-env script.
128 At this point, we assume the build host is set up and
129 <filename>poky</filename> repository has been cloned.
130 </para></listitem>
131 <listitem><para role='writernotes'>
132 Be sure your <filename>local.conf</filename> file has
133 the correct
134 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
135 variable set for the target hardware on which your
136 kernel image runs.
137 Also have the
138 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink>
139 variable set equal to "kernel-modules".
140 </para></listitem>
141 <listitem><para role='writernotes'>
142 Create a layer for later that will contain your patches
143 (if any) to the kernel.
144 </para></listitem>
145 <listitem><para role='writernotes'>
146 Build the extensible SDK.
147 </para></listitem>
148 <listitem><para role='writernotes'>
149 Install the extensible SDK.
150 </para></listitem>
151 <listitem><para role='writernotes'>
152 Set up the terminal so that you can work with the
153 extensible SDK.
154 This terminal is known as the "eSDK Terminal" unlike the
155 terminal that is set up to run BitBake, which is known
156 as the "BitBake Terminal".
157 </para></listitem>
158 <listitem><para role='writernotes'>
159 Build the initial image using the extensible SDK.
160 </para></listitem>
161 </orderedlist>
162 </para>
163
164 <para role='writernotes'>
165 At this point, the user has enough stuff set up to work on the
166 kernel.
167 I will put a section in the "Common Tasks" area of this manual
168 that finished out how to make a modification to the kernel.
125 </para> 169 </para>
126 </section> 170 </section>
127 171