mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-31 00:39:46 +00:00
Code Issues Projects Releases Wiki Activity

documentation: Kernel Manual fixes

Browse Source 
Upgraded to reflect 1.0 usage rather than 0.90 usage, and some other
clarifications and minor changes.

[RP - added tweaks suggested by Darren Hart]
(From OE-Core rev: c6f06f478ac229c4619f815b8b313711d47b1551)

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Tom Zanussi
2011-03-14 00:36:28 -05:00
committed by Richard Purdie
parent 5ef65bd112
commit 4f5b57c67e
1 changed files with 65 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/kernel-manual/kernel-how-to.xml
+65 -59
View File
@@ -425,18 +425,18 @@ repository.
<literallayout class='monospaced'> <literallayout class='monospaced'>
# full description of the changes # full description of the changes
&gt; git whatchanged &lt;kernel type&gt;..&lt;bsp&gt;-&lt;kernel type&gt; &gt; git whatchanged &lt;kernel type&gt;..&lt;kernel type&gt;/&lt;bsp&gt;
&gt; eg: git whatchanged standard..common_pc-standard &gt; eg: git whatchanged yocto/standard/base..yocto/standard/common-pc/base
# summary of the changes # summary of the changes
&gt; git log --pretty=oneline --abbrev-commit &lt;kernel type&gt;..&lt;bsp&gt;-&lt;kernel type&gt; &gt; git log --pretty=oneline --abbrev-commit &lt;kernel type&gt;..&lt;kernel type&gt;/&lt;bsp&gt;
# source code changes (one combined diff) # source code changes (one combined diff)
&gt; git diff &lt;kernel type&gt;..&lt;bsp&gt;-&lt;kernel type&gt; &gt; git diff &lt;kernel type&gt;..&lt;kernel type&gt;/&lt;bsp&gt;
&gt; git show &lt;kernel type&gt;..&lt;bsp&gt;-&lt;kernel type&gt; &gt; git show &lt;kernel type&gt;..&lt;kernel type&gt;/&lt;bsp&gt;
# dump individual patches per commit # dump individual patches per commit
&gt; git format-patch -o &lt;dir&gt; &lt;kernel type&gt;..&lt;bsp&gt;-&lt;kernel type&gt; &gt; git format-patch -o &lt;dir&gt; &lt;kernel type&gt;..&lt;kernel type&gt;/&lt;bsp&gt;
# determine the change history of a particular file # determine the change history of a particular file
&gt; git whatchanged &lt;path to file&gt; &gt; git whatchanged &lt;path to file&gt;
@@ -467,9 +467,9 @@ repository.
# determine which branches contain a feature # determine which branches contain a feature
&gt; git branch --contains &lt;tag&gt; &gt; git branch --contains &lt;tag&gt;
# show the changes in a kernel type - (0.9 examples) # show the changes in a kernel type
&gt; git whatchanged wrs_base..&lt;kernel type&gt; &gt; git whatchanged yocto/base..&lt;kernel type&gt;
&gt; eg: git whatchanged wrs_base..standard &gt; eg: git whatchanged yocto/base..yocto/standard/base
</literallayout> </literallayout>
<para> <para>
@@ -733,10 +733,10 @@ repository.
<para> <para>
For example, the following command pushes the changes from your local branch For example, the following command pushes the changes from your local branch
<filename>common_pc-standard</filename> to the remote branch with the same name <filename>yocto/standard/common-pc/base</filename> to the remote branch with the same name
in the master repository <filename>//git.mycompany.com/pub/git/kernel-2.6.27</filename>. in the master repository <filename>//git.mycompany.com/pub/git/kernel-2.6.37</filename>.
<literallayout class='monospaced'> <literallayout class='monospaced'>
&gt; push ssh://git.mycompany.com/pub/git/kernel-2.6.27 common_pc-standard:common_pc-standard &gt; push ssh://git.mycompany.com/pub/git/kernel-2.6.37 yocto/standard/common-pc/base:yocto/standard/common-pc/base
</literallayout> </literallayout>
</para> </para>
@@ -866,9 +866,9 @@ repository.
<para> <para>
The following commands illustrate some of the steps you could use to The following commands illustrate some of the steps you could use to
import the common_pc-standard kernel into a secondary SCM: import the yocto/standard/common-pc/base kernel into a secondary SCM:
<literallayout class='monospaced'> <literallayout class='monospaced'>
&gt; git checkout common_pc-standard &gt; git checkout yocto/standard/common-pc/base
&gt; cd .. ; echo linux/.git &gt; .cvsignore &gt; cd .. ; echo linux/.git &gt; .cvsignore
&gt; cvs import -m "initial import" linux MY_COMPANY start &gt; cvs import -m "initial import" linux MY_COMPANY start
</literallayout> </literallayout>
@@ -881,8 +881,8 @@ repository.
<para> <para>
The following commands illustrate how you can condense and merge two BSPs into a second SCM: The following commands illustrate how you can condense and merge two BSPs into a second SCM:
<literallayout class='monospaced'> <literallayout class='monospaced'>
&gt; git checkout common_pc-standard &gt; git checkout yocto/standard/common-pc/base
&gt; git merge common_pc_64-standard &gt; git merge yocto/standard/common-pc-64/base
# resolve any conflicts and commit them # resolve any conflicts and commit them
&gt; cd .. ; echo linux/.git &gt; .cvsignore &gt; cd .. ; echo linux/.git &gt; .cvsignore
&gt; cvs import -m "initial import" linux MY_COMPANY start &gt; cvs import -m "initial import" linux MY_COMPANY start
@@ -1006,9 +1006,12 @@ That's it. Configure and build.
<title>Creating a BSP Based on an Existing Similar BSP</title> <title>Creating a BSP Based on an Existing Similar BSP</title>
<para> <para>
This section provides an example for creating a BSP that is based on an existing, and hopefully, This section provides an example for creating a BSP
similar one. that is based on an existing, and hopefully, similar
Follow these steps and keep in mind your particular situation and differences: one. It assumes you will be using a local kernel
repository and will be pointing the kernel recipe at
that. Follow these steps and keep in mind your
particular situation and differences:
<orderedlist> <orderedlist>
<listitem><para> <listitem><para>
@@ -1016,16 +1019,14 @@ That's it. Configure and build.
</para> </para>
<para> <para>
You can start with something in <filename>meta/conf/machine</filename>. You can start with something in <filename>meta/conf/machine</filename> - <filename>
Or, <filename>meta-emenlow/conf/machine</filename> has an example in its own layer. meta/conf/machine/atom-pc.conf</filename> for example. Or, you can start with a machine
configuration from any of the BSP layers in the meta-intel repository at
<ulink url='http://git.pokylinux.org/cgit/cgit.cgi/meta-intel/'></ulink>, such as
<filename>meta-intel/meta-emenlow/conf/machine/emenlow.conf</filename>.
</para> </para>
<para> <para>
The most up-to-date machines that are probably most similar to yours and that you might want
to look at are <filename>meta/conf/machine/atom-pc.conf</filename> and
<filename>meta-emenlow/conf/machine/emenlow.conf</filename>.
Both of these files were either just added or upgraded to use the Yocto Project kernel
at <ulink url='http://git.pokylinux.org/cgit/cgit.cgi/linux-2.6-windriver/'></ulink>.
The main difference between the two is that "emenlow" is in its own layer. The main difference between the two is that "emenlow" is in its own layer.
It is in its own layer because it needs extra machine-specific packages such as its It is in its own layer because it needs extra machine-specific packages such as its
own video driver and other supporting packages. own video driver and other supporting packages.
@@ -1049,19 +1050,21 @@ That's it. Configure and build.
<para> <para>
As an example consider this: As an example consider this:
<itemizedlist> <itemizedlist>
<listitem><para>Copy meta-emenlow</para></listitem> <listitem><para>Copy meta-emenlow to meta-mymachine</para></listitem>
<listitem><para>Fix or remove anything you do not need. <listitem><para>Fix or remove anything you do not need.
For this example the only thing left was the kernel directory with a For this example the only thing left was the kernel directory with a
<filename>linux-yocto-stable_git.bbappend</filename> file <filename>linux-yocto_git.bbappend</filename>
(linux-yocto-stable is the kernel listed in file
<filename>meta-crownbay/conf/machine/crownbay.conf</filename></para></listitem>. and <filename>meta-mymachine/conf/machine/mymachine.conf</filename>
(linux-yocto is the kernel listed in
<filename>meta-emenlow/conf/machine/emenlow.conf</filename>)</para></listitem>.
<listitem><para>Add a new entry in the <filename>build/conf/bblayers.conf</filename> <listitem><para>Add a new entry in the <filename>build/conf/bblayers.conf</filename>
so the new layer can be found by Bitbake.</para></listitem> so the new layer can be found by Bitbake.</para></listitem>
</itemizedlist> </itemizedlist>
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
Get an image with a working kernel built. Create a machine branch for your machine.
</para> </para>
<para> <para>
@@ -1070,58 +1073,52 @@ That's it. Configure and build.
To create this branch first create a bare clone of the Yocto Project git repository. To create this branch first create a bare clone of the Yocto Project git repository.
Next, create a local clone of that: Next, create a local clone of that:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ git clone --bare git://git.pokylinux.org/linux-2.6-windriver.git $ git clone --bare git://git.pokylinux.org/linux-yocto-2.6.37.git
linux-2.6-windriver.git linux-yocto-2.6.37.git
$ git clone linux-2.6-windriver.git linux-2.6-windriver $ git clone linux-yocto-2.6.37.git linux-yocto-2.6.37
</literallayout> </literallayout>
</para> </para>
<para> <para>
Now create a branch in the local clone and push it to the bare clone: Now create a branch in the local clone and push it to the bare clone:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ git checkout -b crownbay-standard origin/standard $ git checkout -b yocto/standard/mymachine origin/yocto/standard/base
$ git push origin crownbay-standard:crownbay-standard $ git push origin yocto/standard/mymachine:yocto/standard/mymachine
</literallayout> </literallayout>
</para>
<para>
At this point, your git tree should compile.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
In a layer, create a <filename>linux-yocto-stable_git.bbappend</filename> In a layer, create a <filename>linux-yocto_git.bbappend</filename>
file with the following: file with the following:
</para> </para>
<para> <para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
COMPATIBLE_MACHINE = ${MACHINE} FILESEXTRAPATHS := "${THISDIR}/${PN}"
COMPATIBLE_MACHINE_mymachine = "mymachine"
# It is often nice to have a local clone of the kernel repository, to # It is often nice to have a local clone of the kernel repository, to
# allow patches to be staged, branches created, and so forth. Modify # allow patches to be staged, branches created, and so forth. Modify
# KSRC to point to your local clone as appropriate. # KSRC to point to your local clone as appropriate.
# KSRC ?= /path/to/your/bare/clone/yocto-kernel KSRC ?= /path/to/your/bare/clone/for/example/linux-yocto-2.6.37.git
# KMACHINE is the branch to be built, or alternateively # KMACHINE is the branch to be built, or alternatively
# KBRANCH can be directly set. # KBRANCH can be directly set.
# KBRANCH is set to KMACHINE in the main linux-yocto_git.bb
# KBRANCH ?= "${LINUX_KERNEL_TYPE}/${KMACHINE}"
# KBRANCH ?= "${KMACHINE}-${LINUX_KERNEL_TYPE}" KMACHINE_mymachine = "yocto/standard/mymachine"
# SRC_URI = "git://${KSRC};nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" SRC_URI = "git://${KSRC};nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
</literallayout> </literallayout>
</para> </para>
<para>
In the previous sample file you need to update and remove the comment from
the KSRC assignment and also remove the comment from the SRC_URI line.
</para>
<para> <para>
After doing that, select the machine in <filename>build/conf/local.conf</filename>: After doing that, select the machine in <filename>build/conf/local.conf</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
# #
MACHINE ?= "crownbay" MACHINE ?= "mymachine"
# #
</literallayout> </literallayout>
</para> </para>
@@ -1131,6 +1128,10 @@ That's it. Configure and build.
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake poky-image-sato-live $ bitbake poky-image-sato-live
</literallayout> </literallayout>
</para></listitem>
<listitem><para>
Modify the kernel configuration for your machine.
</para> </para>
<para> <para>
@@ -1149,17 +1150,22 @@ That's it. Configure and build.
And, another <filename>.cfg</filename> file would contain: And, another <filename>.cfg</filename> file would contain:
<literallayout class='monospaced'> <literallayout class='monospaced'>
CONFIG_LOG_BUF_SHIFT=18 CONFIG_LOG_BUF_SHIFT=18
</literallayout>
http://git.pokylinux.org/cgit/cgit.cgi/linux-2.6-windriver/ <para>
These config fragments could then be picked up and
applied to the kernel .config by appending them to the kernel SRC_URI:
</para>
SRC_URI_append_crownbay = " file://some.cfg \ <literallayout class='monospaced'>
SRC_URI_append_mymachine = " file://some.cfg \
file://other.cfg \ file://other.cfg \
" "
</literallayout> </literallayout>
</para> </para>
<para> <para>
You could also add these directly to the git repository <filename>wrs_meta</filename> You could also add these directly to the git repository <filename>meta</filename>
branch as well. branch as well.
However, the former method is a simple starting point. However, the former method is a simple starting point.
</para></listitem> </para></listitem>
@@ -1173,7 +1179,7 @@ That's it. Configure and build.
<para> <para>
Practically speaking, to generate the patches, you'd go to the source in the build tree: Practically speaking, to generate the patches, you'd go to the source in the build tree:
<literallayout class='monospaced'> <literallayout class='monospaced'>
build/tmp/work/crownbay-poky-linux/linux-yocto-2.6.34+git0+d1cd5c80ee97e81e130be8c3de3965b770f320d6_0+ build/tmp/work/mymachine-poky-linux/linux-yocto-2.6.37+git0+d1cd5c80ee97e81e130be8c3de3965b770f320d6_0+
0431115c9d720fee5bb105f6a7411efb4f851d26-r13/linux 0431115c9d720fee5bb105f6a7411efb4f851d26-r13/linux
</literallayout> </literallayout>
</para> </para>
@@ -1182,7 +1188,7 @@ That's it. Configure and build.
Then, modify the code there, using quilt to save the changes, and recompile until Then, modify the code there, using quilt to save the changes, and recompile until
it works: it works:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake -c compile -f linux-yocto-stable $ bitbake -c compile -f linux-yocto
</literallayout> </literallayout>
</para></listitem> </para></listitem>
@@ -1191,7 +1197,7 @@ That's it. Configure and build.
SRC_URI location. SRC_URI location.
The patch is applied the next time you do a clean build. The patch is applied the next time you do a clean build.
Of course, since you have a branch for the BSP in git, it would be better to put it there instead. Of course, since you have a branch for the BSP in git, it would be better to put it there instead.
For example, in this case, commit the patch to the "crownbay-standard" branch, and during the For example, in this case, commit the patch to the "yocto/standard/mymachine" branch, and during the
next build it is applied from there. next build it is applied from there.
</para></listitem> </para></listitem>
</orderedlist> </orderedlist>