mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-14 03:49:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

kernel-dev: Updates to the traditional kernel development flow section.

Browse Source 
(From yocto-docs rev: d81143d6ae27e2e360f923bde8e578e583a969a1)

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-20 16:53:58 -07:00
committed by Richard Purdie
parent 0767740f32
commit 294dddb6d3
1 changed files with 51 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

92
documentation/kernel-dev/kernel-dev-common.xml
View File

@@ -284,12 +284,14 @@
Before you can do anything using BitBake, you need to 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 a
build environment script build environment script
(i.e. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>oe-init-build-env</filename></ulink> (i.e. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>oe-init-build-env</filename></ulink>).
or
<ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>).
Also, for this example, be sure that the local branch Also, for this example, be sure that the local branch
you have checked out for <filename>poky</filename> is you have checked out for <filename>poky</filename> is
the Yocto Project &DISTRO_NAME; branch: the Yocto Project &DISTRO_NAME; branch.
If you need to checkout out the &DISTRO_NAME; branch,
see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#checking-out-by-branch-in-poky'>Checking out by Branch in Poky</ulink>"
section in the Yocto Project Development Manual.
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ cd ~/poky $ cd ~/poky
$ git branch $ git branch
@@ -534,7 +536,7 @@
<filename>meta-mylayer/recipes-kernel/linux</filename> <filename>meta-mylayer/recipes-kernel/linux</filename>
directory and create the kernel's append file. directory and create the kernel's append file.
This example uses the This example uses the
<filename>linux-yocto_4.12</filename> kernel. <filename>linux-yocto-4.12</filename> kernel.
Thus, the name of the append file is Thus, the name of the append file is
<filename>linux-yocto_4.12.bbappend</filename>: <filename>linux-yocto_4.12.bbappend</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
@@ -1240,12 +1242,6 @@
"<link linkend='getting-ready-for-traditional-kernel-development'>Getting Ready for Traditional Kernel Development</link>" "<link linkend='getting-ready-for-traditional-kernel-development'>Getting Ready for Traditional Kernel Development</link>"
Section. Section.
</note> </note>
</para>
<para>
Also, for more information on patching the kernel, see the
"<link linkend='applying-patches'>Applying Patches</link>"
section.
<orderedlist> <orderedlist>
<listitem><para> <listitem><para>
<emphasis>Edit the Source Files</emphasis> <emphasis>Edit the Source Files</emphasis>
@@ -1338,10 +1334,10 @@
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
<emphasis>Build the Image:</emphasis> <emphasis>Build the Image:</emphasis>
With the source modified, staged, and committed, and With the source modified, your changes staged and
the <filename>local.conf</filename> file pointing to committed, and the <filename>local.conf</filename> file
the kernel files, you can now use BitBake to build the pointing to the kernel files, you can now use BitBake to
image: build the image:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ cd ~/poky/build $ cd ~/poky/build
$ bitbake core-image-minimal $ bitbake core-image-minimal
@@ -1383,47 +1379,61 @@
</literallayout> </literallayout>
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
<emphasis>Make Changes to Use Patch Files During Subsequent Builds:</emphasis> <emphasis>Move the Patch File to Your Layer:</emphasis>
In order for subsequent builds to pick up patches, you In order for subsequent builds to pick up patches, you
need to make some changes in your layer. need to move the patch file you created in the previous
This example created the layer step to your layer <filename>meta-mylayer</filename>.
<filename>meta-mylayer</filename> earlier with basically For this example, the layer created earlier is located
just a <filename>bblayers.conf</filename> file. in your home directory as <filename>meta-mylayer</filename>.
To get it ready for subsequent builds that automatically When the layer was created using the
apply patches, you need to create an kernel recipe append <filename>yocto-create</filename> script, no additional
file.</para> hierarchy was created to support patches.
Before moving the patch file, you need to add additional
<para>Move to the <filename>meta-mylayer</filename> structure to your layer using the following commands:
directory and create some extra structure in your layer:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ cd ~/poky/meta-mylayer $ cd ~/meta-mylayer
$ mkdir recipes-kernel $ mkdir recipes-kernel
$ mkdir recipes-kernel/linux $ mkdir recipes-kernel/linux
$ mkdir recipes-kernel/linux/linux-yocto $ mkdir recipes-kernel/linux/linux-yocto
</literallayout></para> </literallayout>
Once you have created this hierarchy in your layer, you can
<para>In the move the patch file using the following command:
<filename>recipes-kernel/linux/linux-yocto</filename> <literallayout class='monospaced'>
directory, create an append file named $ mv ~/linux-yocto-4.12/init/0001-calibrate.c-Added-some-printk-statements.patch ~/meta-mylayer/recipes-kernel/linux/linux-yocto
<filename>linux-yocto_4.12.bbappend</filename> with the </literallayout>
following contents: </para></listitem>
<listitem><para>
<emphasis>Create the Append File:</emphasis>
Finally, you need to create the
<filename>linux-yocto_4.12.bbappend</filename> file and
insert statements that allow the OpenEmbedded build
system to find the patch.
The append file needs to be in your layer's
<filename>recipes-kernel/linux</filename>
directory and it must be named
<filename>linux-yocto_4.12.bbappend</filename> and have
the following contents:
<literallayout class='monospaced'> <literallayout class='monospaced'>
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://0001-calibrate.c-Added-some-printk-statements.patch" SRC_URI_append = " file://0001-calibrate.c-Added-some-printk-statements.patch"
</literallayout> </literallayout>
The The
<ulink url='&YOCTO_DOCS_REF_URL;var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink>
and and
<ulink url='&YOCTO_DOCS_REF_URL;var-SRC_URI'><filename>SRC_URI</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;var-SRC_URI'><filename>SRC_URI</filename></ulink>
statements enable the OpenEmbedded build system to find statements enable the OpenEmbedded build system to find
the patch file. the patch file.</para>
For more information on using append files, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer"</ulink>"
section in the Yocto Project Development Manual.</para>
<para>Move the patch file you created in the earlier step <para>For more information on append files and patches,
to the TBD see the
"<link linkend='creating-the-append-file'>Creating the Append File</link>"
and
"<link linkend='applying-patches'>Applying Patches</link>"
sections.
You can also see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer"</ulink>"
section in the Yocto Project Development Manual.
</para></listitem> </para></listitem>
</orderedlist> </orderedlist>
</para> </para>