diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index a14dd3b888..1658842597 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -34,12 +34,12 @@ The BSP consists of a file structure inside a base directory. Collectively, you can think of the base directory and the file structure as a BSP Layer. - Although not a strict requirement, layers in the Yocto Project use the + Although not a strict requirement, layers in the Yocto Project use the following well established naming convention: meta-<bsp_name> - The string "meta-" is prepended to the machine or platform name, which is + The string "meta-" is prepended to the machine or platform name, which is "bsp_name" in the above form. @@ -54,7 +54,7 @@ definition and from it build an image. Here is an example: - BBLAYERS = ?" \ + BBLAYERS ?= " \ /usr/local/src/yocto/meta \ /usr/local/src/yocto/meta-yocto \ /usr/local/src/yocto/meta-yocto-bsp \ @@ -261,7 +261,7 @@ This file provides information on where to locate the BSP source files. For example, information provides where to find the sources that comprise the images shipped with the BSP. - Information is also included to help you find the + Information is also included to help you find the Metadata used to generate the images that ship with the BSP. @@ -331,7 +331,7 @@ - To illustrate the string substitutions, here are the corresponding statements + To illustrate the string substitutions, here are the corresponding statements from the Crown Bay conf/layer.conf file: BBFILE_COLLECTIONS += "crownbay" @@ -382,8 +382,8 @@ The crownbay.conf file is used for the Crown Bay BSP that supports the Intel Embedded Media and Graphics Driver (Intel - EMGD), while the crownbay-noemgd file is used for the - Crown Bay BSP that supports Video Electronics Standards Association (VESA) + EMGD), while the crownbay-noemgd file is used for the + Crown Bay BSP that supports Video Electronics Standards Association (VESA) graphics only. @@ -581,7 +581,7 @@ KBRANCH variable to ensure the build process uses the standard/crownbay kernel branch. - The + The KERNEL_FEATURES variable enables features specific to the kernel. Finally, the append file points to specific commits in the @@ -788,7 +788,7 @@ BSP layer maintainer. This is the person to whom patches and questions should be sent. - For information on how to find the right person, see the + For information on how to find the right person, see the "How to Submit a Change" section in the Yocto Project Development Manual. @@ -894,7 +894,7 @@ Create a .bbappend file for the modified recipe. - For information on using append files, see the + For information on using append files, see the "Using .bbappend Files" section in the Yocto Project Development Manual. @@ -903,15 +903,15 @@ that supports your machine is such that it can be found by the build system. See the example later in this section for more information. - + Put the append file in a directory whose name matches the machine's name and is located in an appropriate - sub-directory inside the BSP layer (i.e. + sub-directory inside the BSP layer (i.e. recipes-bsp, recipes-graphics, - recipes-core, and so forth). + recipes-core, and so forth). - Place the BSP-specific files in the directory named for + Place the BSP-specific files in the directory named for your machine inside the BSP layer. @@ -930,7 +930,7 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/files:" PRINC := "${@int(PRINC) + 2}" - The append file needs to be in the + The append file needs to be in the meta-xyz/recipes-core/init-ifupdown directory. Create and place the new interfaces @@ -938,11 +938,11 @@ meta-xyz/recipes-core/init-ifupdown/files/xyz/interfaces - The + The FILESEXTRAPATHS - variable in the append files extends the search path + variable in the append files extends the search path the build system uses to find files during the build. - Consequently, for this example you need to have the + Consequently, for this example you need to have the files directory in the same location as your append file. @@ -978,7 +978,7 @@ For cases where you can substitute a free component and still - maintain the system's functionality, the "Downloads" page from the + maintain the system's functionality, the "Downloads" page from the Yocto Project website's makes available de-featured BSPs that are completely free of any IP encumbrances. @@ -1033,8 +1033,8 @@ can build the encumbered image with no change at all to the normal build process. Get a pre-built version of the BSP: - You can get this type of BSP by visiting the - "Downloads" page of the + You can get this type of BSP by visiting the + "Downloads" page of the Yocto Project website. You can download BSP tarballs that contain proprietary components after agreeing to the licensing @@ -1193,8 +1193,8 @@ the tools. You can also use the yocto-layer tool to create - a "generic" layer. - For information on this tool, see the + a "generic" layer. + For information on this tool, see the "Creating a General Layer Using the yocto-layer Script" section in the Yocto Project Development Guide. @@ -1216,7 +1216,7 @@ by the Yocto Project, as well as QEMU versions of the same. The default mode of the script's operation is to prompt you for information needed to generate the BSP layer. - + For the current set of BSPs, the script prompts you for various important @@ -1271,7 +1271,7 @@ with an invalid response causes the script to accept the default value. Once the script completes, the new meta-myarm BSP layer is created in the current working directory. - This example assumes you have sourced the + This example assumes you have sourced the &OE_INIT_FILE; and are currently in the top-level folder of the Source Directory.