diff options
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r-- | documentation/bsp-guide/bsp.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst index b46773dedd..5c43f53d0c 100644 --- a/documentation/bsp-guide/bsp.rst +++ b/documentation/bsp-guide/bsp.rst | |||
@@ -95,11 +95,11 @@ layer and from it build an image. Here is an example:: | |||
95 | 95 | ||
96 | .. note:: | 96 | .. note:: |
97 | 97 | ||
98 | Ordering and :term:`BBFILE_PRIORITY` for the layers listed in ``BBLAYERS`` | 98 | Ordering and :term:`BBFILE_PRIORITY` for the layers listed in :term:`BBLAYERS` |
99 | matter. For example, if multiple layers define a machine configuration, the | 99 | matter. For example, if multiple layers define a machine configuration, the |
100 | OpenEmbedded build system uses the last layer searched given similar layer | 100 | OpenEmbedded build system uses the last layer searched given similar layer |
101 | priorities. The build system works from the top-down through the layers | 101 | priorities. The build system works from the top-down through the layers |
102 | listed in ``BBLAYERS``. | 102 | listed in :term:`BBLAYERS`. |
103 | 103 | ||
104 | Some BSPs require or depend on additional layers beyond the BSP's root | 104 | Some BSPs require or depend on additional layers beyond the BSP's root |
105 | layer in order to be functional. In this case, you need to specify these | 105 | layer in order to be functional. In this case, you need to specify these |
@@ -685,7 +685,7 @@ statements as follows:: | |||
685 | 685 | ||
686 | .. note:: | 686 | .. note:: |
687 | 687 | ||
688 | When the preferred provider is assumed by default, the ``PREFERRED_PROVIDER`` | 688 | When the preferred provider is assumed by default, the :term:`PREFERRED_PROVIDER` |
689 | statement does not appear in the ``"bsp_root_name".conf`` file. | 689 | statement does not appear in the ``"bsp_root_name".conf`` file. |
690 | 690 | ||
691 | You would use the ``linux-yocto_4.4.bbappend`` file to append specific | 691 | You would use the ``linux-yocto_4.4.bbappend`` file to append specific |
@@ -1121,15 +1121,15 @@ list describes them in order of preference: | |||
1121 | how to use these variables. | 1121 | how to use these variables. |
1122 | 1122 | ||
1123 | If you build as you normally would, without specifying any recipes in | 1123 | If you build as you normally would, without specifying any recipes in |
1124 | the ``LICENSE_FLAGS_WHITELIST``, the build stops and provides you | 1124 | the :term:`LICENSE_FLAGS_WHITELIST`, the build stops and provides you |
1125 | with the list of recipes that you have tried to include in the image | 1125 | with the list of recipes that you have tried to include in the image |
1126 | that need entries in the ``LICENSE_FLAGS_WHITELIST``. Once you enter | 1126 | that need entries in the :term:`LICENSE_FLAGS_WHITELIST`. Once you enter |
1127 | the appropriate license flags into the whitelist, restart the build | 1127 | the appropriate license flags into the whitelist, restart the build |
1128 | to continue where it left off. During the build, the prompt will not | 1128 | to continue where it left off. During the build, the prompt will not |
1129 | appear again since you have satisfied the requirement. | 1129 | appear again since you have satisfied the requirement. |
1130 | 1130 | ||
1131 | Once the appropriate license flags are on the white list in the | 1131 | Once the appropriate license flags are on the white list in the |
1132 | ``LICENSE_FLAGS_WHITELIST`` variable, you can build the encumbered | 1132 | :term:`LICENSE_FLAGS_WHITELIST` variable, you can build the encumbered |
1133 | image with no change at all to the normal build process. | 1133 | image with no change at all to the normal build process. |
1134 | 1134 | ||
1135 | #. *Get a Pre-Built Version of the BSP:* You can get this type of BSP by | 1135 | #. *Get a Pre-Built Version of the BSP:* You can get this type of BSP by |
@@ -1142,7 +1142,7 @@ list describes them in order of preference: | |||
1142 | click-through license agreements presented by the website. If you | 1142 | click-through license agreements presented by the website. If you |
1143 | want to build the image yourself using the recipes contained within | 1143 | want to build the image yourself using the recipes contained within |
1144 | the BSP tarball, you will still need to create an appropriate | 1144 | the BSP tarball, you will still need to create an appropriate |
1145 | ``LICENSE_FLAGS_WHITELIST`` to match the encumbered recipes in the | 1145 | :term:`LICENSE_FLAGS_WHITELIST` to match the encumbered recipes in the |
1146 | BSP. | 1146 | BSP. |
1147 | 1147 | ||
1148 | .. note:: | 1148 | .. note:: |
@@ -1405,7 +1405,7 @@ Project Reference Manual. | |||
1405 | 1405 | ||
1406 | The BeagleBone development board requires an SPL to boot and that SPL | 1406 | The BeagleBone development board requires an SPL to boot and that SPL |
1407 | file type must be MLO. Consequently, the machine configuration needs | 1407 | file type must be MLO. Consequently, the machine configuration needs |
1408 | to define ``SPL_BINARY`` as ``MLO``. | 1408 | to define :term:`SPL_BINARY` as ``MLO``. |
1409 | 1409 | ||
1410 | .. note:: | 1410 | .. note:: |
1411 | 1411 | ||