mirror of
https://git.yoctoproject.org/poky
synced 2026-05-30 00:20:08 +00:00
ref-manual: improve description of kernel-fitimage variables
- Mentioning that they are related to this class (for further information about their usage) - Replace "fitImage" by "FIT image" - Minor formating and style fixes (From yocto-docs rev: 07214a4ff2646efb143a02fc9381a029870e9b56) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> CC: Jamin Lin <jamin_lin@aspeedtech.com> Reviewed-by: Sean Anderson <sean.anderson@seco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
4417a30196
commit
a95cbed77f
@@ -1582,13 +1582,13 @@ The :ref:`ref-classes-kernel-devicetree` class, which is inherited by the
|
||||
===================
|
||||
|
||||
The :ref:`ref-classes-kernel-fitimage` class provides support to pack a kernel image,
|
||||
device trees, a U-boot script, a :term:`Initramfs` bundle and a RAM disk
|
||||
device trees, a U-boot script, an :term:`Initramfs` bundle and a RAM disk
|
||||
into a single FIT image. In theory, a FIT image can support any number
|
||||
of kernels, U-boot scripts, :term:`Initramfs` bundles, RAM disks and device-trees.
|
||||
However, :ref:`ref-classes-kernel-fitimage` currently only supports
|
||||
limited usecases: just one kernel image, an optional U-boot script,
|
||||
an optional :term:`Initramfs` bundle, an optional RAM disk, and any number of
|
||||
device tree.
|
||||
device trees.
|
||||
|
||||
To create a FIT image, it is required that :term:`KERNEL_CLASSES`
|
||||
is set to include ":ref:`ref-classes-kernel-fitimage`" and :term:`KERNEL_IMAGETYPE`
|
||||
|
||||
Reference in New Issue
Block a user