[PATCH] Documentation: booting-linux: document booting specific FIT configuration
Sascha Hauer
sha at pengutronix.de
Tue Mar 28 00:46:39 PDT 2023
On Sun, Mar 26, 2023 at 01:22:11PM +0200, Ahmad Fatoum wrote:
> Apparently, this was so far undocumented, but it's useful in some setups
> where board type is detected dynamically. Document it.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum at pengutronix.de>
> ---
> Documentation/user/booting-linux.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
> index 60babb513cea..a9dd0d67d350 100644
> --- a/Documentation/user/booting-linux.rst
> +++ b/Documentation/user/booting-linux.rst
> @@ -19,8 +19,10 @@ architecture the bootm command handles different image types. On ARM the
> following images are supported:
>
> * ARM Linux zImage
> +* ARM64 Linux Image, plain or compressed
> * U-Boot uImage
> * barebox images
> +* FIT images, containing a zImage or Image
>
> The images can either be passed directly to the bootm command as argument or
> in the ``global.bootm.image`` variable:
> @@ -48,6 +50,14 @@ variable:
> global.bootm.image=/path/to/zImage
> bootm
>
> +FIT image configurations will be matched by comparing the ``compatible`` property
> +inside the configuration node with the barebox live tree's ``/compatible``.
> +It's also possible to select a specific configuration explicitly:
> +
> +.. code-block:: sh
> +
> + global.bootm.image=/dev/mmc0.fit at conf-imx8mm-evk.dtb
> +
> **NOTE:** it may happen that barebox is probed from the devicetree, but you have
> want to start a Kernel without passing a devicetree. In this case set the
> ``global.bootm.boot_atag`` variable to ``true``.
> --
> 2.30.2
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list