|
|
@@ -2983,18 +2983,18 @@ system and gives an overview of their function and contents.
|
|
|
|
|
|
:term:`FIT_ADDRESS_CELLS`
|
|
|
Specifies the value of the ``#address-cells`` value for the
|
|
|
- description of the FIT image.
|
|
|
+ description of the FIT image.
|
|
|
|
|
|
The default value is set to "1" by the :ref:`ref-classes-kernel-fitimage`
|
|
|
- class, which corresponds to 32 bit addresses.
|
|
|
+ class, which corresponds to 32 bit addresses.
|
|
|
|
|
|
For platforms that need to set 64 bit addresses, for example in
|
|
|
:term:`UBOOT_LOADADDRESS` and :term:`UBOOT_ENTRYPOINT`, you need to
|
|
|
- set this value to "2", as two 32 bit values (cells) will be needed
|
|
|
+ set this value to "2", as two 32 bit values (cells) will be needed
|
|
|
to represent such addresses.
|
|
|
|
|
|
Here is an example setting "0x400000000" as a load address::
|
|
|
-
|
|
|
+
|
|
|
FIT_ADDRESS_CELLS = "2"
|
|
|
UBOOT_LOADADDRESS= "0x04 0x00000000"
|
|
|
|
|
|
@@ -3971,15 +3971,15 @@ system and gives an overview of their function and contents.
|
|
|
Specifies a space-separated list of license names (as they would
|
|
|
appear in :term:`LICENSE`) that should be excluded
|
|
|
from the build (if set globally), or from an image (if set locally
|
|
|
- in an image recipe).
|
|
|
+ in an image recipe).
|
|
|
|
|
|
When the variable is set globally, recipes that provide no alternatives to listed
|
|
|
incompatible licenses are not built. Packages that are individually
|
|
|
- licensed with the specified incompatible licenses will be deleted.
|
|
|
+ licensed with the specified incompatible licenses will be deleted.
|
|
|
Most of the time this does not allow a feasible build (because it becomes impossible
|
|
|
to satisfy build time dependencies), so the recommended way to
|
|
|
implement license restrictions is to set the variable in specific
|
|
|
- image recipes where the restrictions must apply. That way there
|
|
|
+ image recipes where the restrictions must apply. That way there
|
|
|
are no build time restrictions, but the license check is still
|
|
|
performed when the image's filesystem is assembled from packages.
|
|
|
|
|
|
@@ -4495,12 +4495,12 @@ system and gives an overview of their function and contents.
|
|
|
When kernel configuration fragments are missing for some
|
|
|
:term:`KERNEL_FEATURES` specified by layers or BSPs,
|
|
|
building and configuring the kernel stops with an error.
|
|
|
-
|
|
|
+
|
|
|
You can turn these errors into warnings by setting the
|
|
|
following in ``conf/local.conf``::
|
|
|
|
|
|
KERNEL_DANGLING_FEATURES_WARN_ONLY = "1"
|
|
|
-
|
|
|
+
|
|
|
You will still be warned that runtime issues may occur,
|
|
|
but at least the kernel configuration and build process will
|
|
|
be allowed to continue.
|
|
|
@@ -7868,7 +7868,7 @@ system and gives an overview of their function and contents.
|
|
|
This option allows to associate `SPDX annotations
|
|
|
<https://spdx.github.io/spdx-spec/v2.3/annotations/>`__ to a recipe,
|
|
|
using the values of variables in the recipe::
|
|
|
-
|
|
|
+
|
|
|
ANNOTATION1 = "First annotation for recipe"
|
|
|
ANNOTATION2 = "Second annotation for recipe"
|
|
|
SPDX_CUSTOM_ANNOTATION_VARS = "ANNOTATION1 ANNOTATION2"
|
|
|
@@ -7991,7 +7991,7 @@ system and gives an overview of their function and contents.
|
|
|
The name of keys used by the :ref:`ref-classes-kernel-fitimage` class
|
|
|
for signing U-Boot FIT image stored in the :term:`SPL_SIGN_KEYDIR`
|
|
|
directory. If we have for example a ``dev.key`` key and a ``dev.crt``
|
|
|
- certificate stored in the :term:`SPL_SIGN_KEYDIR` directory, you will
|
|
|
+ certificate stored in the :term:`SPL_SIGN_KEYDIR` directory, you will
|
|
|
have to set :term:`SPL_SIGN_KEYNAME` to ``dev``.
|
|
|
|
|
|
:term:`SPLASH`
|
|
|
@@ -8028,7 +8028,7 @@ system and gives an overview of their function and contents.
|
|
|
|
|
|
EXTRA_OECONF += "--disable-startup-msg --enable-img-fullscreen"
|
|
|
|
|
|
- For information on append files, see the
|
|
|
+ For information on append files, see the
|
|
|
":ref:`dev-manual/layers:appending other layers metadata with your layer`"
|
|
|
section.
|
|
|
|
|
|
@@ -9442,10 +9442,10 @@ system and gives an overview of their function and contents.
|
|
|
|
|
|
:term:`UBOOT_FIT_ADDRESS_CELLS`
|
|
|
Specifies the value of the ``#address-cells`` value for the
|
|
|
- description of the U-Boot FIT image.
|
|
|
+ description of the U-Boot FIT image.
|
|
|
|
|
|
The default value is set to "1" by the :ref:`ref-classes-uboot-sign`
|
|
|
- class, which corresponds to 32 bit addresses.
|
|
|
+ class, which corresponds to 32 bit addresses.
|
|
|
|
|
|
For platforms that need to set 64 bit addresses in
|
|
|
:term:`UBOOT_LOADADDRESS` and :term:`UBOOT_ENTRYPOINT`, you need to
|
|
|
@@ -9453,7 +9453,7 @@ system and gives an overview of their function and contents.
|
|
|
to represent such addresses.
|
|
|
|
|
|
Here is an example setting "0x400000000" as a load address::
|
|
|
-
|
|
|
+
|
|
|
UBOOT_FIT_ADDRESS_CELLS = "2"
|
|
|
UBOOT_LOADADDRESS= "0x04 0x00000000"
|
|
|
|
|
|
@@ -9516,7 +9516,7 @@ system and gives an overview of their function and contents.
|
|
|
UBOOT_FITIMAGE_ENABLE = "1"
|
|
|
|
|
|
See the :ref:`ref-classes-uboot-sign` class for details.
|
|
|
-
|
|
|
+
|
|
|
:term:`UBOOT_LOADADDRESS`
|
|
|
Specifies the load address for the U-Boot image. During U-Boot image
|
|
|
creation, the :term:`UBOOT_LOADADDRESS` variable is passed as a
|
Michael Opdenacker