mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
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>
This commit is contained in:
committed by
Richard Purdie
parent
5865fcdf85
commit
0fbba0fb46
@@ -452,6 +452,32 @@
|
||||
<section id="using-devtool-to-patch-the-kernel">
|
||||
<title>Using <filename>devtool</filename> to Patch the Kernel</title>
|
||||
|
||||
|
||||
<para role='writernotes'>
|
||||
Some stuff here for the using devtool from the wiki.
|
||||
This whole section is WIP.
|
||||
<orderedlist>
|
||||
<listitem><para role='writernotes'>
|
||||
If you are dealing with real hardware, you can flash the
|
||||
new kernel image to a USB stick and boot the hardware to
|
||||
see it run.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Checkout and modify the kernel source.
|
||||
This is where you make your changes to the image.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Create a new image that uses the altered kernel.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
If you are working with actual hardware, you can flash
|
||||
the new image to a USB stick and use it to boot up the
|
||||
hardware.
|
||||
You can see your changes in action.
|
||||
</para></listitem>
|
||||
</orderedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Patching the kernel involves changing or adding configurations to an existing kernel,
|
||||
changing or adding recipes to the kernel that are needed to support specific hardware features,
|
||||
|
||||
@@ -121,7 +121,51 @@
|
||||
<title>Getting Ready to Develop using <filename>devtool</filename></title>
|
||||
|
||||
<para role='writernotes'>
|
||||
Need the updated wiki stuff here
|
||||
Sections as follows:
|
||||
<orderedlist>
|
||||
<listitem><para role='writernotes'>
|
||||
Source the oe-init-build-env script.
|
||||
At this point, we assume the build host is set up and
|
||||
<filename>poky</filename> repository has been cloned.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Be sure your <filename>local.conf</filename> file has
|
||||
the correct
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
|
||||
variable set for the target hardware on which your
|
||||
kernel image runs.
|
||||
Also have the
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS'><filename>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</filename></ulink>
|
||||
variable set equal to "kernel-modules".
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Create a layer for later that will contain your patches
|
||||
(if any) to the kernel.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Build the extensible SDK.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Install the extensible SDK.
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Set up the terminal so that you can work with the
|
||||
extensible SDK.
|
||||
This terminal is known as the "eSDK Terminal" unlike the
|
||||
terminal that is set up to run BitBake, which is known
|
||||
as the "BitBake Terminal".
|
||||
</para></listitem>
|
||||
<listitem><para role='writernotes'>
|
||||
Build the initial image using the extensible SDK.
|
||||
</para></listitem>
|
||||
</orderedlist>
|
||||
</para>
|
||||
|
||||
<para role='writernotes'>
|
||||
At this point, the user has enough stuff set up to work on the
|
||||
kernel.
|
||||
I will put a section in the "Common Tasks" area of this manual
|
||||
that finished out how to make a modification to the kernel.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user