mirror of
https://git.yoctoproject.org/poky
synced 2026-05-31 12:49:46 +00:00
ref-manual: use consistent capitalisation of U-Boot
Change all instances of U-boot to U-Boot. (From yocto-docs rev: 153c60fd9f2807c8e98105bcd4384e52e2adaa1a) Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
f567cda0a9
commit
07ec4c4ee7
@@ -1391,19 +1391,19 @@ when creating the FIT image are specified using the
|
|||||||
|
|
||||||
Only a single kernel can be added to the FIT image created by
|
Only a single kernel can be added to the FIT image created by
|
||||||
``kernel-fitimage`` and the kernel image in FIT is mandatory. The
|
``kernel-fitimage`` and the kernel image in FIT is mandatory. The
|
||||||
address where the kernel image is to be loaded by U-boot is
|
address where the kernel image is to be loaded by U-Boot is
|
||||||
specified by :term:`UBOOT_LOADADDRESS` and the entrypoint by
|
specified by :term:`UBOOT_LOADADDRESS` and the entrypoint by
|
||||||
:term:`UBOOT_ENTRYPOINT`.
|
:term:`UBOOT_ENTRYPOINT`.
|
||||||
|
|
||||||
Multiple device trees can be added to the FIT image created by
|
Multiple device trees can be added to the FIT image created by
|
||||||
``kernel-fitimage`` and the device tree is optional.
|
``kernel-fitimage`` and the device tree is optional.
|
||||||
The address where the device tree is to be loaded by U-boot is
|
The address where the device tree is to be loaded by U-Boot is
|
||||||
specified by :term:`UBOOT_DTBO_LOADADDRESS` for device tree overlays
|
specified by :term:`UBOOT_DTBO_LOADADDRESS` for device tree overlays
|
||||||
and by :term:`UBOOT_DTB_LOADADDRESS` for device tree binaries.
|
and by :term:`UBOOT_DTB_LOADADDRESS` for device tree binaries.
|
||||||
|
|
||||||
Only a single RAM disk can be added to the FIT image created by
|
Only a single RAM disk can be added to the FIT image created by
|
||||||
``kernel-fitimage`` and the RAM disk in FIT is optional.
|
``kernel-fitimage`` and the RAM disk in FIT is optional.
|
||||||
The address where the RAM disk image is to be loaded by U-boot
|
The address where the RAM disk image is to be loaded by U-Boot
|
||||||
is specified by :term:`UBOOT_RD_LOADADDRESS` and the entrypoint by
|
is specified by :term:`UBOOT_RD_LOADADDRESS` and the entrypoint by
|
||||||
:term:`UBOOT_RD_ENTRYPOINT`. The ramdisk is added to FIT image when
|
:term:`UBOOT_RD_ENTRYPOINT`. The ramdisk is added to FIT image when
|
||||||
:term:`INITRAMFS_IMAGE` is specified.
|
:term:`INITRAMFS_IMAGE` is specified.
|
||||||
|
|||||||
@@ -190,7 +190,7 @@ Removed Recipes
|
|||||||
|
|
||||||
The following recipes have been removed:
|
The following recipes have been removed:
|
||||||
|
|
||||||
- ``x-load``: This recipe has been superseded by U-boot SPL for all
|
- ``x-load``: This recipe has been superseded by U-Boot SPL for all
|
||||||
Cortex-based TI SoCs. For legacy boards, the ``meta-ti`` layer, which
|
Cortex-based TI SoCs. For legacy boards, the ``meta-ti`` layer, which
|
||||||
contains a maintained recipe, should be used instead.
|
contains a maintained recipe, should be used instead.
|
||||||
|
|
||||||
|
|||||||
@@ -8404,21 +8404,21 @@ system and gives an overview of their function and contents.
|
|||||||
In this example, "sd" is selected as the configuration of the possible four for the
|
In this example, "sd" is selected as the configuration of the possible four for the
|
||||||
``UBOOT_MACHINE``. The "sd" configuration defines
|
``UBOOT_MACHINE``. The "sd" configuration defines
|
||||||
"mx6qsabreauto_config" as the value for ``UBOOT_MACHINE``, while the
|
"mx6qsabreauto_config" as the value for ``UBOOT_MACHINE``, while the
|
||||||
"sdcard" specifies the ``IMAGE_FSTYPES`` to use for the U-boot image.
|
"sdcard" specifies the ``IMAGE_FSTYPES`` to use for the U-Boot image.
|
||||||
|
|
||||||
For more information on how the ``UBOOT_CONFIG`` is handled, see the
|
For more information on how the ``UBOOT_CONFIG`` is handled, see the
|
||||||
:ref:`uboot-config <ref-classes-uboot-config>`
|
:ref:`uboot-config <ref-classes-uboot-config>`
|
||||||
class.
|
class.
|
||||||
|
|
||||||
:term:`UBOOT_DTB_LOADADDRESS`
|
:term:`UBOOT_DTB_LOADADDRESS`
|
||||||
Specifies the load address for the dtb image used by U-boot. During FIT
|
Specifies the load address for the dtb image used by U-Boot. During FIT
|
||||||
image creation, the ``UBOOT_DTB_LOADADDRESS`` variable is used in
|
image creation, the ``UBOOT_DTB_LOADADDRESS`` variable is used in
|
||||||
:ref:`kernel-fitimage <ref-classes-kernel-fitimage>` class to specify
|
:ref:`kernel-fitimage <ref-classes-kernel-fitimage>` class to specify
|
||||||
the load address to be used in
|
the load address to be used in
|
||||||
creating the dtb sections of Image Tree Source for the FIT image.
|
creating the dtb sections of Image Tree Source for the FIT image.
|
||||||
|
|
||||||
:term:`UBOOT_DTBO_LOADADDRESS`
|
:term:`UBOOT_DTBO_LOADADDRESS`
|
||||||
Specifies the load address for the dtbo image used by U-boot. During FIT
|
Specifies the load address for the dtbo image used by U-Boot. During FIT
|
||||||
image creation, the ``UBOOT_DTBO_LOADADDRESS`` variable is used in
|
image creation, the ``UBOOT_DTBO_LOADADDRESS`` variable is used in
|
||||||
:ref:`kernel-fitimage <ref-classes-kernel-fitimage>` class to specify the load address to be used in
|
:ref:`kernel-fitimage <ref-classes-kernel-fitimage>` class to specify the load address to be used in
|
||||||
creating the dtbo sections of Image Tree Source for the FIT image.
|
creating the dtbo sections of Image Tree Source for the FIT image.
|
||||||
@@ -8503,7 +8503,7 @@ system and gives an overview of their function and contents.
|
|||||||
certificate used for signing FIT image.
|
certificate used for signing FIT image.
|
||||||
|
|
||||||
:term:`UBOOT_SIGN_KEYNAME`
|
:term:`UBOOT_SIGN_KEYNAME`
|
||||||
The name of keys used for signing U-boot FIT image stored in
|
The name of keys used for signing U-Boot FIT image stored in
|
||||||
:term:`UBOOT_SIGN_KEYDIR` directory. For e.g. dev.key key and dev.crt
|
:term:`UBOOT_SIGN_KEYDIR` directory. For e.g. dev.key key and dev.crt
|
||||||
certificate stored in :term:`UBOOT_SIGN_KEYDIR` directory will have
|
certificate stored in :term:`UBOOT_SIGN_KEYDIR` directory will have
|
||||||
:term:`UBOOT_SIGN_KEYNAME` set to "dev".
|
:term:`UBOOT_SIGN_KEYNAME` set to "dev".
|
||||||
|
|||||||
Reference in New Issue
Block a user