documentation/kernel-manual/kernel-how-to.xml: More changes to the creating BSP section.

These changes implemented Bruce Ashfield's next round of changes to the
section 4.3.3 example.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This commit is contained in:
Scott Rifenbark 2011-02-14 17:04:23 -06:00
parent 05ac368888
commit 647aaad6fb
1 changed files with 17 additions and 12 deletions

View File

@ -1088,21 +1088,26 @@ That's it. Configure and build.
</para></listitem>
<listitem><para>
Point the build at the new kernel git tree.
</para>
In a layer, create a <filename>linux-yocto_git.bbappend</filename>
file with the following:
</para>
<para>
You can do this by commenting out the SRC_URI variable in
<filename>meta/recipes-kernel/linux/linux-yocto_git.bb</filename> and using a SRC_URI
that points to your new bare git tree.
You should also be able to do this in <filename>linux-yocto_git.bbappend</filename> in the layer:
<literallayout class='monospaced'>
# To use a staged, on-disk bare clone of a Wind River Kernel, use a variant of the
# below SRC_URI = "git://///path/to/kernel/default_kernel.git;fullclone=1"
#
SRC_URI = "git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=${KBRANCH};name=machine
\
git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;noclone=1;branch=wrs_meta;name=meta"
COMPATIBLE_MACHINE = ${MACHINE}
# 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
# KSRC to point to your local clone as appropriate.
# KSRC ?= /path/to/your/bare/clone/yocto-kernel
# KMACHINE is the branch to be built, or alternateively
# KBRANCH can be directly set.
# KBRANCH ?= "${KMACHINE}-${LINUX_KERNEL_TYPE}"
# SRC_URI = "git://${KSRC};nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
</literallayout>
</para>