mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-01 13:09:50 +00:00
Code Issues Projects Releases Wiki Activity

bsp-guide, ref-manual: Various fixes from Robert P. J. Day review.

Browse Source 
Robert read through the BSP Guide and noted several issues.
There were several typos, inacurracies for crown bay code,
out-dated kernel usage example, etc.

One change I had to make that was related was to fix two cross-reference
links to a re-named section.  These links were the changes in the
FAQ chapter of the ref-manual.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: ae45df660ebf33105ebf5e60e606b0ec76eb9a6d)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2013-04-22 11:19:36 -07:00
committed by Richard Purdie
parent caa6e079c3
commit 818ec77cd3
2 changed files with 52 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/bsp-guide/bsp.xml
+50 -41
View File
@@ -34,11 +34,13 @@
The BSP consists of a file structure inside a base directory. The BSP consists of a file structure inside a base directory.
Collectively, you can think of the base directory and the file structure Collectively, you can think of the base directory and the file structure
as a BSP Layer. as a BSP Layer.
BSP Layers use the following naming convention: Although not a strict requirement, layers in the Yocto Project use the
following well established naming convention:
<literallayout class='monospaced'> <literallayout class='monospaced'>
meta-&lt;bsp_name&gt; meta-&lt;bsp_name&gt;
</literallayout> </literallayout>
"bsp_name" is a placeholder for the machine or platform name. The string "meta-" is prepended to the machine or platform name, which is
"bsp_name" in the above form.
</para> </para>
<para> <para>
@@ -318,9 +320,9 @@
# We have a conf and classes directory, add to BBPATH # We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}" BBPATH .= ":${LAYERDIR}"
# We have recipes-* directories, add to BBFILES # We have a recipes directory, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*.bb \ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*.bbappend" ${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "bsp" BBFILE_COLLECTIONS += "bsp"
BBFILE_PATTERN_bsp = "^${LAYERDIR}/" BBFILE_PATTERN_bsp = "^${LAYERDIR}/"
@@ -329,8 +331,8 @@
</para> </para>
<para> <para>
To illustrate the string substitutions, here are the last three statements from the Crown To illustrate the string substitutions, here are the corresponding statements
Bay <filename>conf/layer.conf</filename> file: from the Crown Bay <filename>conf/layer.conf</filename> file:
<literallayout class='monospaced'> <literallayout class='monospaced'>
BBFILE_COLLECTIONS += "crownbay" BBFILE_COLLECTIONS += "crownbay"
BBFILE_PATTERN_crownbay = "^${LAYERDIR}/" BBFILE_PATTERN_crownbay = "^${LAYERDIR}/"
@@ -397,9 +399,8 @@
Tuning files are found in the <filename>meta/conf/machine/include</filename> Tuning files are found in the <filename>meta/conf/machine/include</filename>
directory within the directory within the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Tuning files can also reside in the BSP Layer itself.
For example, the <filename>ia32-base.inc</filename> file resides in the For example, the <filename>ia32-base.inc</filename> file resides in the
<filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>. <filename>meta/conf/machine/include</filename> directory.
</para> </para>
<para> <para>
@@ -409,12 +410,13 @@
<literallayout class='monospaced'> <literallayout class='monospaced'>
require conf/machine/include/tune-atom.inc require conf/machine/include/tune-atom.inc
require conf/machine/include/ia32-base.inc require conf/machine/include/ia32-base.inc
require conf/machine/include/meta-intel.inc
</literallayout> </literallayout>
</para> </para>
</section> </section>
<section id='bsp-filelayout-misc-recipes'> <section id='bsp-filelayout-misc-recipes'>
<title>Miscellaneous Recipe Files</title> <title>Miscellaneous BSP-Specific Recipe Files</title>
<para> <para>
You can find these files in the BSP Layer at: You can find these files in the BSP Layer at:
<literallayout class='monospaced'> <literallayout class='monospaced'>
@@ -500,28 +502,28 @@
the <filename>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename> directory). the <filename>meta-&lt;bsp_name&gt;/recipes-kernel/linux</filename> directory).
</para> </para>
<para> <para>
Suppose you are using the <filename>linux-yocto_3.4.bb</filename> recipe to build Suppose you are using the <filename>linux-yocto_3.8.bb</filename> recipe to build
the kernel. the kernel.
In other words, you have selected the kernel in your In other words, you have selected the kernel in your
<filename>&lt;bsp_name&gt;.conf</filename> file by adding these types <filename>&lt;bsp_name&gt;.conf</filename> file by adding these types
of statements: of statements:
<literallayout class='monospaced'> <literallayout class='monospaced'>
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
PREFERRED_VERSION_linux-yocto = "3.4%" PREFERRED_VERSION_linux-yocto ?= "3.8%"
</literallayout> </literallayout>
<note> <note>
When the preferred provider is assumed by default, the When the preferred provider is assumed by default, the
<filename>PREFERRED_PROVIDER</filename> statement does not appear in the <filename>PREFERRED_PROVIDER</filename> statement does not appear in the
<filename>&lt;bsp_name&gt;.conf</filename> file. <filename>&lt;bsp_name&gt;.conf</filename> file.
</note> </note>
You would use the <filename>linux-yocto_3.4.bbappend</filename> file to append You would use the <filename>linux-yocto_3.8.bbappend</filename> file to append
specific BSP settings to the kernel, thus configuring the kernel for your particular BSP. specific BSP settings to the kernel, thus configuring the kernel for your particular BSP.
</para> </para>
<para> <para>
As an example, look at the existing Crown Bay BSP. As an example, look at the existing Crown Bay BSP.
The append file used is: The append file used is:
<literallayout class='monospaced'> <literallayout class='monospaced'>
meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend meta-crownbay/recipes-kernel/linux/linux-yocto_3.8.bbappend
</literallayout> </literallayout>
The following listing shows the file. The following listing shows the file.
Be aware that the actual commit ID strings in this example listing might be different Be aware that the actual commit ID strings in this example listing might be different
@@ -531,40 +533,43 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_crownbay = "crownbay" COMPATIBLE_MACHINE_crownbay = "crownbay"
KMACHINE_crownbay = "crownbay" KMACHINE_crownbay = "crownbay"
KBRANCH_crownbay = "standard/crownbay" KBRANCH_crownbay = "standard/crownbay"
KERNEL_FEATURES_crownbay_append = " features/drm-emgd/drm-emgd-1.16 cfg/vesafb"
COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd" COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd"
KMACHINE_crownbay-noemgd = "crownbay" KMACHINE_crownbay-noemgd = "crownbay"
KBRANCH_crownbay-noemgd = "standard/crownbay" KBRANCH_crownbay-noemgd = "standard/crownbay"
KERNEL_FEATURES_crownbay-noemgd_append = " cfg/vesafb"
SRCREV_machine_pn-linux-yocto_crownbay ?= "449f7f520350700858f21a5554b81cc8ad23267d" LINUX_VERSION = "3.8.4"
SRCREV_meta_pn-linux-yocto_crownbay ?= "9e3bdb7344054264b750e53fbbb6394cc1c942ac"
SRCREV_emgd_pn-linux-yocto_crownbay ?= "86643bdd8cbad616a161ab91f51108cf0da827bc"
SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?= "449f7f520350700858f21a5554b81cc8ad23267d" SRCREV_meta_crownbay = "2a6d36e75ca0a121570a389d7bab76ec240cbfda"
SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?= "9e3bdb7344054264b750e53fbbb6394cc1c942ac" SRCREV_machine_crownbay = "47aed0c17c1c55988198ad39f86ae88894c8e0a4"
SRCREV_emgd_crownbay = "c780732f175ff0ec866fac2130175876b519b576"
KSRC_linux_yocto_3_4 ?= "git.yoctoproject.org/linux-yocto-3.4.git" SRCREV_meta_crownbay-noemgd = "2a6d36e75ca0a121570a389d7bab76ec240cbfda"
SRC_URI_crownbay = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta,emgd-1.14;name=machine,meta,emgd" SRCREV_machine_crownbay-noemgd = "47aed0c17c1c55988198ad39f86ae88894c8e0a4"
SRC_URI_crownbay-noemgd = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
SRC_URI_crownbay = "git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},emgd-1.16;name=machine,meta,emgd"
</literallayout> </literallayout>
This append file contains statements used to support the Crown Bay BSP for both This append file contains statements used to support the Crown Bay BSP for both
<trademark class='registered'>Intel</trademark> EMGD and the VESA graphics. <trademark class='registered'>Intel</trademark> EMGD and the VESA graphics.
The build process, in this case, recognizes and uses only the statements that The build process, in this case, recognizes and uses only the statements that
apply to the defined machine name - <filename>crownbay</filename> in this case. apply to the defined machine name - <filename>crownbay</filename> in this case.
So, the applicable statements in the <filename>linux-yocto_3.4.bbappend</filename> So, the applicable statements in the <filename>linux-yocto_3.8.bbappend</filename>
file are follows: file are follows:
<literallayout class='monospaced'> <literallayout class='monospaced'>
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_crownbay = "crownbay" COMPATIBLE_MACHINE_crownbay = "crownbay"
KMACHINE_crownbay = "crownbay" KMACHINE_crownbay = "crownbay"
KBRANCH_crownbay = "standard/crownbay" KBRANCH_crownbay = "standard/crownbay"
KERNEL_FEATURES_crownbay_append = " features/drm-emgd/drm-emgd-1.16 cfg/vesafb"
SRCREV_machine_pn-linux-yocto_crownbay ?= "449f7f520350700858f21a5554b81cc8ad23267d" SRCREV_meta_crownbay = "2a6d36e75ca0a121570a389d7bab76ec240cbfda"
SRCREV_meta_pn-linux-yocto_crownbay ?= "9e3bdb7344054264b750e53fbbb6394cc1c942ac" SRCREV_machine_crownbay = "47aed0c17c1c55988198ad39f86ae88894c8e0a4"
SRCREV_emgd_pn-linux-yocto_crownbay ?= "86643bdd8cbad616a161ab91f51108cf0da827bc" SRCREV_emgd_crownbay = "c780732f175ff0ec866fac2130175876b519b576"
</literallayout> </literallayout>
The append file defines <filename>crownbay</filename> as the The append file defines <filename>crownbay</filename> as the
<ulink url='&YOCTO_DOCS_REF_URL;#var-COMPATIBLE_MACHINE'><filename>COMPATIBLE_MACHINE</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-COMPATIBLE_MACHINE'><filename>COMPATIBLE_MACHINE</filename></ulink>
@@ -574,8 +579,11 @@
machine name used by the Linux Yocto kernel. machine name used by the Linux Yocto kernel.
The file also uses the optional The file also uses the optional
<ulink url='&YOCTO_DOCS_REF_URL;#var-KBRANCH'><filename>KBRANCH</filename></ulink> variable <ulink url='&YOCTO_DOCS_REF_URL;#var-KBRANCH'><filename>KBRANCH</filename></ulink> variable
to ensure the build process uses the <filename>standard/default/crownbay</filename> to ensure the build process uses the <filename>standard/crownbay</filename>
kernel branch. kernel branch.
The
<ulink url='&YOCTO_DOCS_REF_URL;#var-KERNEL_FEATURES'><filename>KERNEL_FEATURES</filename></ulink>
variable enables features specific to the kernel.
Finally, the append file points to specific commits in the Finally, the append file points to specific commits in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> Git <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> Git
repository and the <filename>meta</filename> Git repository branches to identify the repository and the <filename>meta</filename> Git repository branches to identify the
@@ -601,7 +609,7 @@
</para> </para>
<para> <para>
For example, suppose you had a some configuration options in a file called For example, suppose you had some configuration options in a file called
<filename>network_configs.cfg</filename>. <filename>network_configs.cfg</filename>.
You can place that file inside a directory named <filename>/linux-yocto</filename> and then add You can place that file inside a directory named <filename>/linux-yocto</filename> and then add
a <filename>SRC_URI</filename> statement such as the following to the append file. a <filename>SRC_URI</filename> statement such as the following to the append file.
@@ -723,7 +731,7 @@
as outlined in <filename>recipes.txt</filename>. as outlined in <filename>recipes.txt</filename>.
If you cannot find a category in <filename>recipes.txt</filename> If you cannot find a category in <filename>recipes.txt</filename>
to fit a particular recipe, you can make up your own to fit a particular recipe, you can make up your own
<filename>recipe-*</filename> subdirectory. <filename>recipes-*</filename> subdirectory.
You can find <filename>recipes.txt</filename> in the You can find <filename>recipes.txt</filename> in the
<filename>meta</filename> directory of the <filename>meta</filename> directory of the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
@@ -811,9 +819,9 @@
This file identifies the <filename>meta-&lt;bsp_name&gt;</filename> This file identifies the <filename>meta-&lt;bsp_name&gt;</filename>
BSP layer as a layer to the build system.</para></listitem> BSP layer as a layer to the build system.</para></listitem>
<listitem><para><emphasis>Machine Configuration File:</emphasis> <listitem><para><emphasis>Machine Configuration File:</emphasis>
You must include a <filename>conf/machine/&lt;bsp_name&gt;.conf</filename> You must include one or more <filename>conf/machine/&lt;bsp_name&gt;.conf</filename>
in the <filename>meta-&lt;bsp_name&gt;</filename> directory. files in the <filename>meta-&lt;bsp_name&gt;</filename> directory.
This configuration file defines a machine target that can be built These configuration files define machine targets that can be built
using the BSP layer. using the BSP layer.
Multiple machine configuration files define variations of machine Multiple machine configuration files define variations of machine
configurations that are supported by the BSP. configurations that are supported by the BSP.
@@ -827,7 +835,8 @@
<note>It is completely possible for a developer to structure the <note>It is completely possible for a developer to structure the
working repository as a conglomeration of unrelated BSP working repository as a conglomeration of unrelated BSP
files, and to possibly generate BSPs targeted for release files, and to possibly generate BSPs targeted for release
from that directory using scripts or some other mechanism. from that directory using scripts or some other mechanism
(e.g. <filename>meta-yocto-bsp</filename> layer).
Such considerations are outside the scope of this document.</note> Such considerations are outside the scope of this document.</note>
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
@@ -1259,7 +1268,7 @@
As the <filename>yocto-bsp create</filename> command runs, default values for As the <filename>yocto-bsp create</filename> command runs, default values for
the prompts appear in brackets. the prompts appear in brackets.
Pressing enter without supplying anything on the command line or pressing enter Pressing enter without supplying anything on the command line or pressing enter
and providing an invalid response causes the script to accept the default value. with an invalid response causes the script to accept the default value.
Once the script completes, the new <filename>meta-myarm</filename> BSP layer Once the script completes, the new <filename>meta-myarm</filename> BSP layer
is created in the current working directory. is created in the current working directory.
This example assumes you have sourced the This example assumes you have sourced the
@@ -1350,7 +1359,7 @@
<filename>bblayers.conf</filename> file. <filename>bblayers.conf</filename> file.
Here is an example: Here is an example:
<literallayout class='monospaced'> <literallayout class='monospaced'>
BBLAYERS = ?" \ BBLAYERS = ? " \
/usr/local/src/yocto/meta \ /usr/local/src/yocto/meta \
/usr/local/src/yocto/meta-yocto \ /usr/local/src/yocto/meta-yocto \
/usr/local/src/yocto/meta-yocto-bsp \ /usr/local/src/yocto/meta-yocto-bsp \
documentation/ref-manual/faq.xml
+2 -2
View File
@@ -407,7 +407,7 @@
<answer> <answer>
<para> <para>
You need to create a form factor file as described in the You need to create a form factor file as described in the
"<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</ulink>" "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous BSP-Specific Recipe Files</ulink>"
section in the Yocto Project Board Support Packages (BSP) section in the Yocto Project Board Support Packages (BSP)
Developer's Guide. Developer's Guide.
Set the <filename>HAVE_TOUCHSCREEN</filename> variable equal to Set the <filename>HAVE_TOUCHSCREEN</filename> variable equal to
@@ -431,7 +431,7 @@
automatically bring up network interfaces. automatically bring up network interfaces.
Therefore, you will need to add a BSP-specific netbase that includes an interfaces Therefore, you will need to add a BSP-specific netbase that includes an interfaces
file. file.
See the "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</ulink>" See the "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous BSP-Specific Recipe Files</ulink>"
section in the Yocto Project Board Support Packages (BSP) section in the Yocto Project Board Support Packages (BSP)
Developer's Guide for information on creating these types of Developer's Guide for information on creating these types of
miscellaneous recipe files. miscellaneous recipe files.