mirror of
https://git.yoctoproject.org/poky
synced 2026-05-30 12:29:55 +00:00
kernel-dev: Updates to "Using Kernel Metadata in a Recipe"
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:
committed by
Richard Purdie
parent
94e71dea32
commit
99151aef77
@@ -44,20 +44,18 @@
|
|||||||
<title>Using Kernel Metadata in a Recipe</title>
|
<title>Using Kernel Metadata in a Recipe</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The kernel sources in the Yocto Project contain kernel Metadata, which
|
As mentioned in the introduction, the Yocto Project contains kernel
|
||||||
is located in the <filename>meta</filename> branches of the kernel
|
Metadata, which is located in the
|
||||||
source Git repositories.
|
<filename>yocto-kernel-cache</filename> Git repository.
|
||||||
This Metadata defines Board Support Packages (BSPs) that
|
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
|
A BSP consists of an aggregation of kernel policy and enabled
|
||||||
hardware-specific features.
|
hardware-specific features.
|
||||||
The BSP can be influenced from within the linux-yocto recipe.
|
The BSP can be influenced from within the linux-yocto recipe.
|
||||||
<note>
|
<note>
|
||||||
Linux kernel source that contains kernel Metadata is said to be
|
A Linux kernel recipe that contains kernel Metadata (e.g.
|
||||||
"linux-yocto style" kernel source.
|
inherits from the <filename>linux-yocto.inc</filename> file)
|
||||||
A Linux kernel recipe that inherits from the
|
is said to be a "linux-yocto style" recipe.
|
||||||
<filename>linux-yocto.inc</filename> include file is said to be a
|
|
||||||
"linux-yocto style" recipe.
|
|
||||||
</note>
|
</note>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
@@ -92,9 +90,9 @@
|
|||||||
<note>
|
<note>
|
||||||
You can use the <filename>KBRANCH</filename> value to define an
|
You can use the <filename>KBRANCH</filename> value to define an
|
||||||
alternate branch typically with a machine override as shown here
|
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'>
|
<literallayout class='monospaced'>
|
||||||
KBRANCH_emenlow-noemgd = "standard/base"
|
KBRANCH_edgerouter = "standard/edgerouter"
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</note>
|
</note>
|
||||||
</para>
|
</para>
|
||||||
@@ -133,16 +131,7 @@
|
|||||||
recipe.
|
recipe.
|
||||||
The tools use the first BSP description it finds that match
|
The tools use the first BSP description it finds that match
|
||||||
both variables.
|
both variables.
|
||||||
If the tools cannot find a match, they issue a warning such as
|
If the tools cannot find a match, they issue a warning.
|
||||||
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".
|
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|||||||
Reference in New Issue
Block a user