kernel-dev: Edits to the devtool kernel development method.

Changes based on a run through of the procedure.

(From yocto-docs rev: 0a526bb15f597843d1e5da1eeca0a952c6c5016f)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2017-09-21 16:55:18 -07:00
committed by Richard Purdie
parent b673c3b990
commit 8f7df8648a

View File

@@ -70,7 +70,7 @@
<listitem><para>
<emphasis>Initialize the BitBake Environment:</emphasis>
Before building an extensible SDK, you need to
initialize the BitBake build environment by sourcing a
initialize the BitBake build environment by sourcing the
build environment script
(i.e. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>oe-init-build-env</filename></ulink>):
<literallayout class='monospaced'>
@@ -155,8 +155,8 @@
</para></listitem>
<listitem><para>
<emphasis>Build the Extensible SDK:</emphasis>
Use BitBake to build the extensible SDK specifically for
the Minnowboard:
Use BitBake to build the extensible SDK specifically
for use with images to be run using QEMU:
<literallayout class='monospaced'>
$ cd ~/poky/build
$ bitbake core-image-minimal -c populate_sdk_ext
@@ -280,7 +280,7 @@
<listitem><para>
<emphasis>Initialize the BitBake Environment:</emphasis>
Before you can do anything using BitBake, you need to
initialize the BitBake build environment by sourcing a
initialize the BitBake build environment by sourcing the
build environment script
(i.e. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>oe-init-build-env</filename></ulink>).
Also, for this example, be sure that the local branch
@@ -1009,14 +1009,6 @@
"<link linkend='getting-ready-to-develop-using-devtool'>Getting Ready to Develop using <filename>devtool</filename></link>"
Section.
</note>
</para>
<para>
Also, for more information on patching the kernel, see the
"<link linkend='applying-patches'>Applying Patches</link>"
section.
</para>
<orderedlist>
<listitem><para>
<emphasis>Check Out the Kernel Source Files:</emphasis>
@@ -1156,7 +1148,7 @@
</literallayout>
</para></listitem>
<listitem><para>
<emphasis>Export the Patches and Create a <filename>.bbappend</filename>:</emphasis>
<emphasis>Export the Patches and Create an Append File:</emphasis>
To export your commits as patches and create a
<filename>.bbappend</filename> file, use the following
command in the terminal used to work with the extensible
@@ -1169,7 +1161,7 @@
section for information on setting up this layer.
</note>
<literallayout class='monospaced'>
$ devtool finish linux-yocto /path/to/meta-mylayer
$ devtool finish linux-yocto ~/meta-mylayer
</literallayout>
Once the command finishes, the patches and the
<filename>.bbappend</filename> file are located in the
@@ -1189,6 +1181,7 @@
</literallayout>
</para></listitem>
</orderedlist>
</para>
</section>
<section id="using-traditional-kernel-development-to-patch-the-kernel">
@@ -1441,8 +1434,8 @@
following sequence of commands:
<literallayout class='monospaced'>
$ cd ~/poky/build
$ cd bitbake -c cleanall yocto-linux
$ cd bitbake core-image-minimal -c cleanall
$ bitbake -c cleanall yocto-linux
$ bitbake core-image-minimal -c cleanall
$ bitbake core-image-minimal
$ runqemu qemux86
</literallayout>