mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-01-29 21:08:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

kernel-dev: Updates to "Using Kernel Metadata in a Recipe"

Browse Source 
This section had some old emenlo examples and was a little
confusing.  I removed the old examples and inserted some new
wordings to help smooth it out.

(From yocto-docs rev: 365129e0cd37772f404d96a51eb498210e4f1ee9)

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-10-02 12:59:32 -07:00
committed by Richard Purdie
parent 94e71dea32
commit 99151aef77
1 changed files with 10 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
documentation/kernel-dev/kernel-dev-advanced.xml
View File

@@ -44,20 +44,18 @@
<title>Using Kernel Metadata in a Recipe</title>
<para>
The kernel sources in the Yocto Project contain kernel Metadata, which
is located in the <filename>meta</filename> branches of the kernel
source Git repositories.
As mentioned in the introduction, the Yocto Project contains kernel
Metadata, which is located in the
<filename>yocto-kernel-cache</filename> Git repository.
This Metadata defines Board Support Packages (BSPs) that
correspond to definitions in linux-yocto recipes for the same BSPs.
correspond to definitions in linux-yocto recipes for corresponding BSPs.
A BSP consists of an aggregation of kernel policy and enabled
hardware-specific features.
The BSP can be influenced from within the linux-yocto recipe.
<note>
Linux kernel source that contains kernel Metadata is said to be
"linux-yocto style" kernel source.
A Linux kernel recipe that inherits from the
<filename>linux-yocto.inc</filename> include file is said to be a
"linux-yocto style" recipe.
A Linux kernel recipe that contains kernel Metadata (e.g.
inherits from the <filename>linux-yocto.inc</filename> file)
is said to be a "linux-yocto style" recipe.
</note>
</para>
@@ -92,9 +90,9 @@
<note>
You can use the <filename>KBRANCH</filename> value to define an
alternate branch typically with a machine override as shown here
from the <filename>meta-emenlow</filename> layer:
from the <filename>meta-yocto-bsp</filename> layer:
<literallayout class='monospaced'>
KBRANCH_emenlow-noemgd = "standard/base"
KBRANCH_edgerouter = "standard/edgerouter"
</literallayout>
</note>
</para>
@@ -133,16 +131,7 @@
recipe.
The tools use the first BSP description it finds that match
both variables.
If the tools cannot find a match, they issue a warning such as
the following:
<literallayout class='monospaced'>
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at meta/cfg/broken/emenlow-broken/hdw_frags.txt and
meta/cfg/broken/emenlow-broken/required_frags.txt in directory:
meta/cfg/broken/emenlow-broken
</literallayout>
In this example, <filename>KMACHINE</filename> was set to "emenlow-broken"
and <filename>LINUX_KERNEL_TYPE</filename> was set to "broken".
If the tools cannot find a match, they issue a warning.
</para>
<para>