[PATCH 0/9] Fix various typos, wording or whitespace errors

[PATCH 0/9] Fix various typos, wording or whitespace errors

[Wolfgang Wallner]

While reading through the U-Boot source code and documentation, i stumbled
over some typos and similar errors like wrong formating. These are the commits
where I collected the fixes.



Wolfgang Wallner (9):
  doc: develop: Fix typos in binman/binman.rst
  doc: develop: Change formatting to make binman doc more readable
  doc: Fix typos
  boot: kconfig: Fix typos
  image: Fix typos in image.h
  bootm: Fix typo in bootm.h
  boot: Fix typo
  doc: Fix whitespace in devicetree example in overlay-fdt-boot.rst
  doc: develop: virtio: Fix qemu example (true/false -> on/off)

 boot/Kconfig                           |   4 +-
 boot/image-fit.c                       |   2 +-
 doc/develop/devicetree/control.rst     |   2 +-
 doc/develop/driver-model/fdt-fixup.rst |   2 +-
 doc/develop/driver-model/virtio.rst    |   4 +-
 doc/develop/testing.rst                |   4 +-
 doc/develop/trace.rst                  |   2 +-
 doc/mkimage.1                          |   4 +-
 doc/usage/environment.rst              |   2 +-
 doc/usage/fit/beaglebone_vboot.rst     |   2 +-
 doc/usage/fit/overlay-fdt-boot.rst     | 156 ++++++++++++-------------
 include/bootm.h                        |   2 +-
 include/image.h                        |   8 +-
 tools/binman/binman.rst                |  73 ++++++------
 14 files changed, 136 insertions(+), 131 deletions(-)

-- 
2.51.1

base-commit: b10c055d4e1b5153a331a61ef82a5b01b5bb4c45
branch: us/fix_typos

[PATCH 1/9] doc: develop: Fix typos in binman/binman.rst

[Wolfgang Wallner]

Fix some typos in binman.rst.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>

---

 tools/binman/binman.rst | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 392e507d449..2d81f0115c0 100644
--- a/tools/binman/binman.rst
+++ b/tools/binman/binman.rst
@@ -272,7 +272,7 @@ Then, in practice binman is often used twice:
 - Once within the U-Boot build system, for development and testing
 - Again, outside U-Boot to assembly and final production images
 
-While the same input binaries are used in each case, you will of course you will
+While the same input binaries are used in each case, you will of course
 need to create your own binman command line, like that in `cmd_binman` in
 the Makefile. You may find the -I and --toolpath options useful. The
 devicetree file is provided to binman in binary form, so there is no need to
@@ -1184,7 +1184,7 @@ size is written to the node in an 'uncomp-size' property, if -u is used.
 
 Compression is also supported for sections. In that case the entire section is
 compressed in one block, including all its contents. This means that accessing
-an entry from the section required decompressing the entire section. Also, the
+an entry from the section requires decompressing the entire section. Also, the
 size of a section indicates the space that it consumes in its parent section
 (and typically the image). With compression, the section may contain more data,
 and the uncomp-size property indicates that, as above. The contents of the
@@ -1224,8 +1224,8 @@ If you are having trouble figuring out what is going on, you can use
 Templates
 =========
 
-Sometimes multiple images need to be created which have all have a common
-part. For example, a board may generate SPI and eMMC images which both include
+Sometimes multiple images need to be created which all have a common part.
+For example, a board may generate SPI and eMMC images which both include
 a FIT. Since the FIT includes many entries, it is tedious to repeat them twice
 in the image description.
 
@@ -1250,7 +1250,7 @@ Templates provide a simple way to handle this::
 
             /* things specific to SPI follow */
             footer {
-            ];
+            };
 
             text {
                 text = "SPI image";
@@ -1263,7 +1263,7 @@ Templates provide a simple way to handle this::
 
             /* things specific to MMC follow */
             footer {
-            ];
+            };
 
             text {
                 text = "MMC image";
@@ -1330,9 +1330,9 @@ Updating an ELF file
 
 For the EFI app, where U-Boot is loaded from UEFI and runs as an app, there is
 no way to update the devicetree after U-Boot is built. Normally this works by
-creating a new u-boot.dtb.out with he updated devicetree, which is automatically
+creating a new u-boot.dtb.out with the updated devicetree, which is automatically
 built into the output image. With ELF this is not possible since the ELF is
-not part of an image, just a stand-along file. We must create an updated ELF
+not part of an image, just a stand-alone file. We must create an updated ELF
 file with the new devicetree.
 
 This is handled by the --update-fdt-in-elf option. It takes four arguments,
@@ -1450,7 +1450,7 @@ or just a selection::
     $ binman extract -i image.bin "*u-boot*" -O outdir
 
 Some entry types have alternative formats, for example fdtmap which allows
-extracted just the devicetree binary without the fdtmap header::
+extracting just the devicetree binary without the fdtmap header::
 
     $ binman extract -i /tmp/b/odroid-c4/image.bin -f out.dtb -F fdt fdtmap
     $ fdtdump out.dtb
@@ -1488,7 +1488,7 @@ that there is an 'fdtmap' entry in the image. For example::
     $ binman replace -i image.bin section/cbfs/u-boot
 
 which will write the contents of the file 'u-boot' from the current directory
-to the that entry, compressing if necessary. If the entry size changes, you must
+to that entry, compressing if necessary. If the entry size changes, you must
 add the 'allow-repack' property to the original image before generating it (see
 above), otherwise you will get an error.
 
@@ -1517,27 +1517,27 @@ original offset and size properties of each entry, if any were specified, in
 the 'orig-offset' and 'orig-size' properties. This allows Binman to distinguish
 between an entry which ended up being packed at an offset (or assigned a size)
 and an entry which had a particular offset / size requested in the Binman
-configuration. Where are particular offset / size was requested, this is treated
+configuration. Where a particular offset / size was requested, this is treated
 as set in stone, so Binman will ensure it doesn't change. Without this feature,
 repacking an entry might cause it to disobey the original constraints provided
 when it was created.
 
 
-Signing FIT container with private key in an image
---------------------------------------------------
+Signing a FIT container with private key in an image
+----------------------------------------------------
 
-You can sign FIT container with private key in your image.
+You can sign a FIT container with private key in your image.
 For example::
 
     $ binman sign -i image.bin -k privatekey -a sha256,rsa4096 fit
 
-binman will extract FIT container, sign and replace it immediately.
+binman will extract the FIT container, sign and replace it immediately.
 
-If you want to sign and replace FIT container in place::
+If you want to sign and replace a FIT container in place::
 
     $ binman sign -i image.bin -k privatekey -a sha256,rsa4096 -f fit.fit fit
 
-which will sign FIT container with private key and replace it immediately
+which will sign the FIT container with a private key and replace it immediately
 inside your image.
 
 .. _`BinmanLogging`:
-- 
2.51.1

Re: [PATCH 1/9] doc: develop: Fix typos in binman/binman.rst

[Simon Glass]

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Fix some typos in binman.rst.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
>
> ---
>
>  tools/binman/binman.rst | 34 +++++++++++++++++-----------------
>  1 file changed, 17 insertions(+), 17 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

[PATCH 2/9] doc: develop: Change formatting to make binman doc more readable

[Wolfgang Wallner]

Change the formatting of binman.rst so that the compiled HTML output
becomes more readable. Changes include enumerations and the escaping of
arguments starting with a double dash (e.g. --debug).

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 tools/binman/binman.rst | 39 ++++++++++++++++++++++-----------------
 1 file changed, 22 insertions(+), 17 deletions(-)

diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 2d81f0115c0..3f725868c8b 100644
--- a/tools/binman/binman.rst
+++ b/tools/binman/binman.rst
@@ -1338,12 +1338,17 @@ file with the new devicetree.
 This is handled by the --update-fdt-in-elf option. It takes four arguments,
 separated by comma:
 
-   infile     - filename of input ELF file, e.g. 'u-boot's
-   outfile    - filename of output ELF file, e.g. 'u-boot.out'
-   begin_sym - symbol at the start of the embedded devicetree, e.g.
-   '__dtb_dt_begin'
-   end_sym   - symbol at the start of the embedded devicetree, e.g.
-   '__dtb_dt_end'
+infile:
+    filename of input ELF file, e.g. 'u-boot's
+
+outfile:
+    filename of output ELF file, e.g. 'u-boot.out'
+
+begin_sym:
+    symbol at the start of the embedded devicetree, e.g. '__dtb_dt_begin'
+
+end_sym:
+    symbol at the start of the embedded devicetree, e.g. '__dtb_dt_end'
 
 When this flag is used, U-Boot does all the normal packaging, but as an
 additional step, it creates a new ELF file with the new devicetree embedded in
@@ -1546,19 +1551,19 @@ Logging
 -------
 
 Binman normally operates silently unless there is an error, in which case it
-just displays the error. The -D/--debug option can be used to create a full
+just displays the error. The ``-D/--debug`` option can be used to create a full
 backtrace when errors occur. You can use BINMAN_DEBUG=1 when building to select
 this.
 
 Internally binman logs some output while it is running. This can be displayed
-by increasing the -v/--verbosity from the default of 1:
+by increasing the ``-v/--verbosity`` from the default of 1:
 
-   0: silent
-   1: warnings only
-   2: notices (important messages)
-   3: info about major operations
-   4: detailed information about each operation
-   5: debug (all output)
+   - 0: silent
+   - 1: warnings only
+   - 2: notices (important messages)
+   - 3: info about major operations
+   - 4: detailed information about each operation
+   - 5: debug (all output)
 
 You can use BINMAN_VERBOSE=5 (for example) when building to select this.
 
@@ -1616,19 +1621,19 @@ To fetch tools which are missing, use::
 
     binman tool --fetch missing
 
-You can also use `--fetch all` to fetch all tools or `--fetch <tool>` to fetch
+You can also use ``--fetch all`` to fetch all tools or ``--fetch <tool>`` to fetch
 a particular tool. Some tools are built from source code, in which case you will
 need to have at least the `build-essential` and `git` packages installed.
 
 Tools are fetched into the `~/.binman-tools` directory. This directory is
-automatically added to the toolpath so there is no need to use `--toolpath` to
+automatically added to the toolpath so there is no need to use ``--toolpath`` to
 specify it. If you want to use these tools outside binman, you may want to
 add this directory to your `PATH`. For example, if you use bash, add this to
 the end of `.bashrc`::
 
    PATH="$HOME/.binman-tools:$PATH"
 
-To select a custom directory, use the `--tooldir` option.
+To select a custom directory, use the ``--tooldir`` option.
 
 Bintool Documentation
 =====================
-- 
2.51.1

Re: [PATCH 2/9] doc: develop: Change formatting to make binman doc more readable

[Simon Glass]

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Change the formatting of binman.rst so that the compiled HTML output
> becomes more readable. Changes include enumerations and the escaping of
> arguments starting with a double dash (e.g. --debug).
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
>
>  tools/binman/binman.rst | 39 ++++++++++++++++++++++-----------------
>  1 file changed, 22 insertions(+), 17 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

[PATCH 3/9] doc: Fix typos

[Wolfgang Wallner]

Fix typos/wording in various files in doc/.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 doc/develop/devicetree/control.rst     |  2 +-
 doc/develop/driver-model/fdt-fixup.rst |  2 +-
 doc/develop/testing.rst                |  4 ++--
 doc/develop/trace.rst                  |  2 +-
 doc/mkimage.1                          |  4 ++--
 doc/usage/environment.rst              |  2 +-
 doc/usage/fit/beaglebone_vboot.rst     |  2 +-
 doc/usage/fit/overlay-fdt-boot.rst     | 14 +++++++-------
 8 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/doc/develop/devicetree/control.rst b/doc/develop/devicetree/control.rst
index c25b98683f8..634114af59a 100644
--- a/doc/develop/devicetree/control.rst
+++ b/doc/develop/devicetree/control.rst
@@ -288,7 +288,7 @@ The full devicetree is available to U-Boot proper, but normally only a subset
 Using several DTBs in the SPL (SPL_MULTI_DTB_FIT Kconfig option)
 ----------------------------------------------------------------
 In some rare cases it is desirable to let SPL be able to select one DTB among
-many. This usually not very useful as the DTB for the SPL is small and usually
+many. This is usually not very useful as the DTB for the SPL is small and usually
 fits several platforms. However the DTB sometimes include information that do
 work on several platforms (like IO tuning parameters).
 In this case it is possible to use SPL_MULTI_DTB_FIT Kconfig option. This option
diff --git a/doc/develop/driver-model/fdt-fixup.rst b/doc/develop/driver-model/fdt-fixup.rst
index 974c09031ed..b547daf79ff 100644
--- a/doc/develop/driver-model/fdt-fixup.rst
+++ b/doc/develop/driver-model/fdt-fixup.rst
@@ -45,7 +45,7 @@ An additional problem with the device tree in U-Boot is that it is read-only,
 and the current mechanisms don't allow easy manipulation of the device tree
 after the driver model has been initialized. While migrating to a live device
 tree (at least after the relocation) would greatly simplify the solution of
-this problem, it is a non-negligible task to implement it, an a interim
+this problem, it is a non-negligible task to implement it, an ad interim
 solution is needed to address the problem at least in the medium-term.
 
 Hence, we propose a solution to this problem by offering a board-specific
diff --git a/doc/develop/testing.rst b/doc/develop/testing.rst
index aa7786c99fd..3a2b496fa00 100644
--- a/doc/develop/testing.rst
+++ b/doc/develop/testing.rst
@@ -28,7 +28,7 @@ run. Type this::
 
     make tcheck
 
-You can also run a selection tests in parallel with::
+You can also run a selection of tests in parallel with::
 
     make pcheck
 
@@ -39,7 +39,7 @@ are run. See :doc:`pytest/usage` for more information.
 Sandbox
 -------
 U-Boot can be built as a user-space application (e.g. for Linux). This
-allows test to be executed without needing target hardware. The 'sandbox'
+allows tests to be executed without needing target hardware. The 'sandbox'
 target provides this feature and it is widely used in tests.
 
 See :doc:`tests_sandbox` for more information.
diff --git a/doc/develop/trace.rst b/doc/develop/trace.rst
index d3c8628d124..16635d6d238 100644
--- a/doc/develop/trace.rst
+++ b/doc/develop/trace.rst
@@ -354,7 +354,7 @@ Writing Out Trace Data
 ----------------------
 
 Once the trace data is in an output buffer in memory there are various ways
-to transmit it to the host. Notably you can use tftput to send the data
+to transmit it to the host. Notably you can use tftpput to send the data
 over a network link::
 
     fakegocmd=trace pause; usb start; set autoload n; bootp;
diff --git a/doc/mkimage.1 b/doc/mkimage.1
index 75b6b48a0cf..c705218d345 100644
--- a/doc/mkimage.1
+++ b/doc/mkimage.1
@@ -208,7 +208,7 @@ option and the format of their configuration are listed in
 .TQ
 .BI \-\-secondary\-config " secondary-configuration"
 Some image types support a second set of configuration data. The image types
-which support secondary configuration and the formap of their configuration are
+which support secondary configuration and the format of their configuration are
 listed in
 .BR CONFIGURATION .
 .
@@ -396,7 +396,7 @@ when used together with -K and/or -k options.
 .BI \-\-key\-dest " key-destination"
 Specifies a compiled device tree binary file (typically .dtb) to write
 public key information into. When a private key is used to sign an image,
-the corresponding public key is written into this file for for run-time
+the corresponding public key is written into this file for run-time
 verification. Typically the file here is the device tree binary used by
 CONFIG_OF_CONTROL in U-Boot.
 .
diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
index 5553a629e42..0143f81f2c0 100644
--- a/doc/usage/environment.rst
+++ b/doc/usage/environment.rst
@@ -213,7 +213,7 @@ updatefile
 
 autoload
     if set to "no" (any string beginning with 'n'),
-    "bootp" and "dhcp" will just load perform a lookup of the
+    "bootp" and "dhcp" will just perform a lookup of the
     configuration from the BOOTP server, but not try to
     load any image.
 
diff --git a/doc/usage/fit/beaglebone_vboot.rst b/doc/usage/fit/beaglebone_vboot.rst
index 1298ba1ae08..b15399441ee 100644
--- a/doc/usage/fit/beaglebone_vboot.rst
+++ b/doc/usage/fit/beaglebone_vboot.rst
@@ -473,7 +473,7 @@ you sign::
 Here we are overriding the normal device tree file with our one, which
 contains the public key.
 
-Now you have a special U-Boot image with the public key. It can verify can
+Now you have a special U-Boot image with the public key. It can verify any
 kernel that you sign with the private key as in step 5.
 
 If you like you can take a look at the public key information that mkimage
diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst
index d687e98ea2a..f5af6d9df05 100644
--- a/doc/usage/fit/overlay-fdt-boot.rst
+++ b/doc/usage/fit/overlay-fdt-boot.rst
@@ -19,7 +19,7 @@ Configuration without overlays
 ------------------------------
 
 Take a hypothetical board named 'foo' where there are different supported
-revisions, reva and revb. Assume that both board revisions can use add a bar
+revisions, reva and revb. Assume that both board revisions can add a bar
 add-on board, while only the revb board can use a baz add-on board.
 
 Without using overlays the configuration would be as follows for every case::
@@ -97,7 +97,7 @@ Without using overlays the configuration would be as follows for every case::
 	};
 
 Note the blob needs to be compiled for each case and the combinatorial explosion of
-configurations. A typical device tree blob is in the low hunderds of kbytes so a
+configurations. A typical device tree blob is in the low hundreds of kbytes so a
 multitude of configuration grows the image quite a bit.
 
 Booting this image is done by using::
@@ -117,7 +117,7 @@ Configuration using overlays
 ----------------------------
 
 Device tree overlays can be applied to a base DT and result in the same blob
-being passed to the booting kernel. This saves on space and avoid the combinatorial
+being passed to the booting kernel. This saves on space and avoids the combinatorial
 explosion problem::
 
     /dts-v1/;
@@ -164,7 +164,7 @@ explosion problem::
         };
 
         configurations {
-            default = "foo-reva.dtb;
+            default = "foo-reva.dtb";
             foo-reva.dtb {
                 kernel = "kernel";
                 fdt = "fdt-1", "fdt-2";
@@ -209,9 +209,9 @@ to be writeable.
 Configuration using overlays and feature selection
 --------------------------------------------------
 
-Although the configuration in the previous section works is a bit inflexible
-since it requires all possible configuration options to be laid out before
-hand in the FIT image. For the add-on boards the extra config selection method
+Although the configuration in the previous section works, it is a bit inflexible
+since it requires all possible configuration options to be laid out beforehand
+in the FIT image. For the add-on boards the extra config selection method
 might make sense.
 
 Note the two bar & baz configuration nodes. To boot a reva board with
-- 
2.51.1

Re: [PATCH 3/9] doc: Fix typos

[E Shattow]

On 10/24/25 08:11, Wolfgang Wallner wrote:
> Fix typos/wording in various files in doc/.
> 
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
> 
>  doc/develop/devicetree/control.rst     |  2 +-
>  doc/develop/driver-model/fdt-fixup.rst |  2 +-
>  doc/develop/testing.rst                |  4 ++--
>  doc/develop/trace.rst                  |  2 +-
>  doc/mkimage.1                          |  4 ++--
>  doc/usage/environment.rst              |  2 +-
>  doc/usage/fit/beaglebone_vboot.rst     |  2 +-
>  doc/usage/fit/overlay-fdt-boot.rst     | 14 +++++++-------
>  8 files changed, 16 insertions(+), 16 deletions(-)
> 
> diff --git a/doc/develop/devicetree/control.rst b/doc/develop/devicetree/control.rst
> index c25b98683f8..634114af59a 100644
> --- a/doc/develop/devicetree/control.rst
> +++ b/doc/develop/devicetree/control.rst
> @@ -288,7 +288,7 @@ The full devicetree is available to U-Boot proper, but normally only a subset
>  Using several DTBs in the SPL (SPL_MULTI_DTB_FIT Kconfig option)
>  ----------------------------------------------------------------
>  In some rare cases it is desirable to let SPL be able to select one DTB among
> -many. This usually not very useful as the DTB for the SPL is small and usually
> +many. This is usually not very useful as the DTB for the SPL is small and usually
>  fits several platforms. However the DTB sometimes include information that do
>  work on several platforms (like IO tuning parameters).
>  In this case it is possible to use SPL_MULTI_DTB_FIT Kconfig option. This option
> diff --git a/doc/develop/driver-model/fdt-fixup.rst b/doc/develop/driver-model/fdt-fixup.rst
> index 974c09031ed..b547daf79ff 100644
> --- a/doc/develop/driver-model/fdt-fixup.rst
> +++ b/doc/develop/driver-model/fdt-fixup.rst
> @@ -45,7 +45,7 @@ An additional problem with the device tree in U-Boot is that it is read-only,
>  and the current mechanisms don't allow easy manipulation of the device tree
>  after the driver model has been initialized. While migrating to a live device
>  tree (at least after the relocation) would greatly simplify the solution of
> -this problem, it is a non-negligible task to implement it, an a interim
> +this problem, it is a non-negligible task to implement it, an ad interim
>  solution is needed to address the problem at least in the medium-term.
>  
>  Hence, we propose a solution to this problem by offering a board-specific
> diff --git a/doc/develop/testing.rst b/doc/develop/testing.rst
> index aa7786c99fd..3a2b496fa00 100644
> --- a/doc/develop/testing.rst
> +++ b/doc/develop/testing.rst
> @@ -28,7 +28,7 @@ run. Type this::
>  
>      make tcheck
>  
> -You can also run a selection tests in parallel with::
> +You can also run a selection of tests in parallel with::
>  
>      make pcheck
>  
> @@ -39,7 +39,7 @@ are run. See :doc:`pytest/usage` for more information.
>  Sandbox
>  -------
>  U-Boot can be built as a user-space application (e.g. for Linux). This
> -allows test to be executed without needing target hardware. The 'sandbox'
> +allows tests to be executed without needing target hardware. The 'sandbox'
>  target provides this feature and it is widely used in tests.
>  
>  See :doc:`tests_sandbox` for more information.
> diff --git a/doc/develop/trace.rst b/doc/develop/trace.rst
> index d3c8628d124..16635d6d238 100644
> --- a/doc/develop/trace.rst
> +++ b/doc/develop/trace.rst
> @@ -354,7 +354,7 @@ Writing Out Trace Data
>  ----------------------
>  
>  Once the trace data is in an output buffer in memory there are various ways
> -to transmit it to the host. Notably you can use tftput to send the data
> +to transmit it to the host. Notably you can use tftpput to send the data
>  over a network link::
>  
>      fakegocmd=trace pause; usb start; set autoload n; bootp;
> diff --git a/doc/mkimage.1 b/doc/mkimage.1
> index 75b6b48a0cf..c705218d345 100644
> --- a/doc/mkimage.1
> +++ b/doc/mkimage.1
> @@ -208,7 +208,7 @@ option and the format of their configuration are listed in
>  .TQ
>  .BI \-\-secondary\-config " secondary-configuration"
>  Some image types support a second set of configuration data. The image types
> -which support secondary configuration and the formap of their configuration are
> +which support secondary configuration and the format of their configuration are
>  listed in
>  .BR CONFIGURATION .
>  .
> @@ -396,7 +396,7 @@ when used together with -K and/or -k options.
>  .BI \-\-key\-dest " key-destination"
>  Specifies a compiled device tree binary file (typically .dtb) to write
>  public key information into. When a private key is used to sign an image,
> -the corresponding public key is written into this file for for run-time
> +the corresponding public key is written into this file for run-time
>  verification. Typically the file here is the device tree binary used by
>  CONFIG_OF_CONTROL in U-Boot.
>  .
> diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
> index 5553a629e42..0143f81f2c0 100644
> --- a/doc/usage/environment.rst
> +++ b/doc/usage/environment.rst
> @@ -213,7 +213,7 @@ updatefile
>  
>  autoload
>      if set to "no" (any string beginning with 'n'),
> -    "bootp" and "dhcp" will just load perform a lookup of the
> +    "bootp" and "dhcp" will just perform a lookup of the
>      configuration from the BOOTP server, but not try to
>      load any image.
>  
> diff --git a/doc/usage/fit/beaglebone_vboot.rst b/doc/usage/fit/beaglebone_vboot.rst
> index 1298ba1ae08..b15399441ee 100644
> --- a/doc/usage/fit/beaglebone_vboot.rst
> +++ b/doc/usage/fit/beaglebone_vboot.rst
> @@ -473,7 +473,7 @@ you sign::
>  Here we are overriding the normal device tree file with our one, which
>  contains the public key.
>  
> -Now you have a special U-Boot image with the public key. It can verify can
> +Now you have a special U-Boot image with the public key. It can verify any
>  kernel that you sign with the private key as in step 5.
>  
>  If you like you can take a look at the public key information that mkimage
> diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst
> index d687e98ea2a..f5af6d9df05 100644
> --- a/doc/usage/fit/overlay-fdt-boot.rst
> +++ b/doc/usage/fit/overlay-fdt-boot.rst
> @@ -19,7 +19,7 @@ Configuration without overlays
>  ------------------------------
>  
>  Take a hypothetical board named 'foo' where there are different supported
> -revisions, reva and revb. Assume that both board revisions can use add a bar
> +revisions, reva and revb. Assume that both board revisions can add a bar
>  add-on board, while only the revb board can use a baz add-on board.
>  
>  Without using overlays the configuration would be as follows for every case::
> @@ -97,7 +97,7 @@ Without using overlays the configuration would be as follows for every case::
>  	};
>  
>  Note the blob needs to be compiled for each case and the combinatorial explosion of
> -configurations. A typical device tree blob is in the low hunderds of kbytes so a
> +configurations. A typical device tree blob is in the low hundreds of kbytes so a
>  multitude of configuration grows the image quite a bit.
>  
>  Booting this image is done by using::
> @@ -117,7 +117,7 @@ Configuration using overlays
>  ----------------------------
>  
>  Device tree overlays can be applied to a base DT and result in the same blob
> -being passed to the booting kernel. This saves on space and avoid the combinatorial
> +being passed to the booting kernel. This saves on space and avoids the combinatorial
>  explosion problem::
>  
>      /dts-v1/;
> @@ -164,7 +164,7 @@ explosion problem::
>          };
>  
>          configurations {
> -            default = "foo-reva.dtb;
> +            default = "foo-reva.dtb";
>              foo-reva.dtb {
>                  kernel = "kernel";
>                  fdt = "fdt-1", "fdt-2";
> @@ -209,9 +209,9 @@ to be writeable.
>  Configuration using overlays and feature selection
>  --------------------------------------------------
>  
> -Although the configuration in the previous section works is a bit inflexible
> -since it requires all possible configuration options to be laid out before
> -hand in the FIT image. For the add-on boards the extra config selection method
> +Although the configuration in the previous section works, it is a bit inflexible
> +since it requires all possible configuration options to be laid out beforehand
> +in the FIT image. For the add-on boards the extra config selection method
>  might make sense.
>  
>  Note the two bar & baz configuration nodes. To boot a reva board with

Thanks for doing this work,

Reviewed-by: E Shattow <e@freeshell.de>

[PATCH 4/9] boot: kconfig: Fix typos

[Wolfgang Wallner]

Fix typos in boot/Kconfig.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 boot/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/boot/Kconfig b/boot/Kconfig
index 022ec05de0a..9adb051400f 100644
--- a/boot/Kconfig
+++ b/boot/Kconfig
@@ -1780,7 +1780,7 @@ menu "Image support"
 config IMAGE_PRE_LOAD
 	bool "Image pre-load support"
 	help
-	  Enable an image pre-load stage in the SPL.
+	  Enable an image pre-load stage.
 	  This pre-load stage allows to do some manipulation
 	  or check (for example signature check) on an image
 	  before launching it.
@@ -1812,7 +1812,7 @@ config IMAGE_PRE_LOAD_SIG
 	  u-boot.
 
 config SPL_IMAGE_PRE_LOAD_SIG
-	bool "Image pre-load signature support witin SPL"
+	bool "Image pre-load signature support within SPL"
 	depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
 	select SPL_FIT_SIGNATURE
 	select SPL_RSA
-- 
2.51.1

Re: [PATCH 4/9] boot: kconfig: Fix typos

[Simon Glass]

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Fix typos in boot/Kconfig.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
>
>  boot/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

Re: [PATCH 4/9] boot: kconfig: Fix typos

[Mattijs Korpershoek]

Hi Wolfgang,

Thank you for the patch.

On Fri, Oct 24, 2025 at 17:12, "Wolfgang Wallner" <wolfgang.wallner@br-automation.com> wrote:

> Fix typos in boot/Kconfig.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>

> ---
>
>  boot/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/boot/Kconfig b/boot/Kconfig
> index 022ec05de0a..9adb051400f 100644
> --- a/boot/Kconfig
> +++ b/boot/Kconfig
> @@ -1780,7 +1780,7 @@ menu "Image support"
>  config IMAGE_PRE_LOAD
>  	bool "Image pre-load support"
>  	help
> -	  Enable an image pre-load stage in the SPL.
> +	  Enable an image pre-load stage.
>  	  This pre-load stage allows to do some manipulation
>  	  or check (for example signature check) on an image
>  	  before launching it.
> @@ -1812,7 +1812,7 @@ config IMAGE_PRE_LOAD_SIG
>  	  u-boot.
>  
>  config SPL_IMAGE_PRE_LOAD_SIG
> -	bool "Image pre-load signature support witin SPL"
> +	bool "Image pre-load signature support within SPL"
>  	depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG
>  	select SPL_FIT_SIGNATURE
>  	select SPL_RSA
> -- 
> 2.51.1

[PATCH 5/9] image: Fix typos in image.h

[Wolfgang Wallner]

Fix some typos in include/image.h.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 include/image.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/image.h b/include/image.h
index fc2f2487095..9a1c828416d 100644
--- a/include/image.h
+++ b/include/image.h
@@ -654,10 +654,10 @@ int boot_get_fpga(struct bootm_headers *images);
  * boot_get_ramdisk() is responsible for finding a valid ramdisk image.
  * Currently supported are the following ramdisk sources:
  *      - multicomponent kernel/ramdisk image,
- *      - commandline provided address of decicated ramdisk image.
+ *      - commandline provided address of dedicated ramdisk image.
  *
  * returns:
- *     0, if ramdisk image was found and valid, or skiped
+ *     0, if ramdisk image was found and valid, or skipped
  *     rd_start and rd_end are set to ramdisk start/end addresses if
  *     ramdisk image is found and valid
  *
@@ -739,7 +739,7 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr,
  * @param bootstage_id	ID of starting bootstage to use for progress updates.
  *			This will be added to the BOOTSTAGE_SUB values when
  *			calling bootstage_mark()
- * @param load_op	Decribes what to do with the load address
+ * @param load_op	Describes what to do with the load address
  * @param datap		Returns address of loaded image
  * @param lenp		Returns length of loaded image
  * Return: node offset of image, or -ve error code on error:
@@ -812,7 +812,7 @@ int fit_get_node_from_config(struct bootm_headers *images,
  * boot_get_fdt() is responsible for finding a valid flat device tree image.
  * Currently supported are the following FDT sources:
  *      - multicomponent kernel/ramdisk/FDT image,
- *      - commandline provided address of decicated FDT image.
+ *      - commandline provided address of dedicated FDT image.
  *
  * Return:
  *     0, if fdt image was found and valid, or skipped
-- 
2.51.1

Re: [PATCH 5/9] image: Fix typos in image.h

[Simon Glass]

Hi Wolfgang,

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Fix some typos in include/image.h.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
>
>  include/image.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>

> diff --git a/include/image.h b/include/image.h
> index fc2f2487095..9a1c828416d 100644
> --- a/include/image.h
> +++ b/include/image.h
> @@ -654,10 +654,10 @@ int boot_get_fpga(struct bootm_headers *images);
>   * boot_get_ramdisk() is responsible for finding a valid ramdisk image.
>   * Currently supported are the following ramdisk sources:
>   *      - multicomponent kernel/ramdisk image,
> - *      - commandline provided address of decicated ramdisk image.
> + *      - commandline provided address of dedicated ramdisk image.

It would be better with a hyphen: commandline-provided

>   *
>   * returns:
> - *     0, if ramdisk image was found and valid, or skiped
> + *     0, if ramdisk image was found and valid, or skipped
>   *     rd_start and rd_end are set to ramdisk start/end addresses if
>   *     ramdisk image is found and valid
>   *
> @@ -739,7 +739,7 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr,
>   * @param bootstage_id ID of starting bootstage to use for progress updates.
>   *                     This will be added to the BOOTSTAGE_SUB values when
>   *                     calling bootstage_mark()
> - * @param load_op      Decribes what to do with the load address
> + * @param load_op      Describes what to do with the load address
>   * @param datap                Returns address of loaded image
>   * @param lenp         Returns length of loaded image
>   * Return: node offset of image, or -ve error code on error:
> @@ -812,7 +812,7 @@ int fit_get_node_from_config(struct bootm_headers *images,
>   * boot_get_fdt() is responsible for finding a valid flat device tree image.
>   * Currently supported are the following FDT sources:
>   *      - multicomponent kernel/ramdisk/FDT image,
> - *      - commandline provided address of decicated FDT image.
> + *      - commandline provided address of dedicated FDT image.
>   *
>   * Return:
>   *     0, if fdt image was found and valid, or skipped
> --
> 2.51.1
>

Regards,
Simon

Re: [PATCH 5/9] image: Fix typos in image.h

[Mattijs Korpershoek]

Hi Wolfgang,

Thank you for the patch.

On Fri, Oct 24, 2025 at 17:12, "Wolfgang Wallner" <wolfgang.wallner@br-automation.com> wrote:

> Fix some typos in include/image.h.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>

> ---
>
>  include/image.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/image.h b/include/image.h
> index fc2f2487095..9a1c828416d 100644
> --- a/include/image.h
> +++ b/include/image.h
> @@ -654,10 +654,10 @@ int boot_get_fpga(struct bootm_headers *images);
>   * boot_get_ramdisk() is responsible for finding a valid ramdisk image.
>   * Currently supported are the following ramdisk sources:
>   *      - multicomponent kernel/ramdisk image,
> - *      - commandline provided address of decicated ramdisk image.
> + *      - commandline provided address of dedicated ramdisk image.
>   *
>   * returns:
> - *     0, if ramdisk image was found and valid, or skiped
> + *     0, if ramdisk image was found and valid, or skipped
>   *     rd_start and rd_end are set to ramdisk start/end addresses if
>   *     ramdisk image is found and valid
>   *
> @@ -739,7 +739,7 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr,
>   * @param bootstage_id	ID of starting bootstage to use for progress updates.
>   *			This will be added to the BOOTSTAGE_SUB values when
>   *			calling bootstage_mark()
> - * @param load_op	Decribes what to do with the load address
> + * @param load_op	Describes what to do with the load address
>   * @param datap		Returns address of loaded image
>   * @param lenp		Returns length of loaded image
>   * Return: node offset of image, or -ve error code on error:
> @@ -812,7 +812,7 @@ int fit_get_node_from_config(struct bootm_headers *images,
>   * boot_get_fdt() is responsible for finding a valid flat device tree image.
>   * Currently supported are the following FDT sources:
>   *      - multicomponent kernel/ramdisk/FDT image,
> - *      - commandline provided address of decicated FDT image.
> + *      - commandline provided address of dedicated FDT image.
>   *
>   * Return:
>   *     0, if fdt image was found and valid, or skipped
> -- 
> 2.51.1

[PATCH 6/9] bootm: Fix typo in bootm.h

[Wolfgang Wallner]

Fix a typo in include/bootm.h.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 include/bootm.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/bootm.h b/include/bootm.h
index 61160705215..4060cec7fc0 100644
--- a/include/bootm.h
+++ b/include/bootm.h
@@ -25,7 +25,7 @@ struct cmd_tbl;
  * @addr_img: Address of image to bootm, as passed to
  *	genimg_get_kernel_addr_fit() for processing:
  *
- *    NULL: Usees default load address, i.e. image_load_addr
+ *    NULL: Uses default load address, i.e. image_load_addr
  *    <addr>: Uses hex address
  *
  * For FIT:
-- 
2.51.1

Re: [PATCH 6/9] bootm: Fix typo in bootm.h

[Simon Glass]

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Fix a typo in include/bootm.h.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
>
>  include/bootm.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

[PATCH 7/9] boot: Fix typo

[Wolfgang Wallner]

Fix a typo in image-fit.c.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 boot/image-fit.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/boot/image-fit.c b/boot/image-fit.c
index 41ab1f552b0..2f2d3e9304d 100644
--- a/boot/image-fit.c
+++ b/boot/image-fit.c
@@ -1662,7 +1662,7 @@ int fit_check_format(const void *fit, ulong size)
 
 	if (CONFIG_IS_ENABLED(FIT_FULL_CHECK)) {
 		/*
-		 * If we are not given the size, make do wtih calculating it.
+		 * If we are not given the size, make do with calculating it.
 		 * This is not as secure, so we should consider a flag to
 		 * control this.
 		 */
-- 
2.51.1

Re: [PATCH 7/9] boot: Fix typo

[Simon Glass]

On Fri, 24 Oct 2025 at 16:12, Wolfgang Wallner
<wolfgang.wallner@br-automation.com> wrote:
>
> Fix a typo in image-fit.c.
>
> Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
> ---
>
>  boot/image-fit.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>

[PATCH 8/9] doc: Fix whitespace in devicetree example in overlay-fdt-boot.rst

[Wolfgang Wallner]

Fix the whitespace and add a missing quotation mark
(default = "foo-reva.dtb") in overlay-fdt-boot.rst.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 doc/usage/fit/overlay-fdt-boot.rst | 142 ++++++++++++++---------------
 1 file changed, 71 insertions(+), 71 deletions(-)

diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst
index f5af6d9df05..0f012d6988a 100644
--- a/doc/usage/fit/overlay-fdt-boot.rst
+++ b/doc/usage/fit/overlay-fdt-boot.rst
@@ -24,77 +24,77 @@ add-on board, while only the revb board can use a baz add-on board.
 
 Without using overlays the configuration would be as follows for every case::
 
-	/dts-v1/;
-	/ {
-	    images {
-	    kernel {
-		data = /incbin/("./zImage");
-		type = "kernel";
-		arch = "arm";
-		os = "linux";
-		load = <0x82000000>;
-		entry = <0x82000000>;
-	    };
-	    fdt-1 {
-		data = /incbin/("./foo-reva.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    fdt-2 {
-		data = /incbin/("./foo-revb.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    fdt-3 {
-		data = /incbin/("./foo-reva-bar.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    fdt-4 {
-		data = /incbin/("./foo-revb-bar.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    fdt-5 {
-		data = /incbin/("./foo-revb-baz.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    fdt-6 {
-		data = /incbin/("./foo-revb-bar-baz.dtb");
-		type = "flat_dt";
-		arch = "arm";
-	    };
-	    };
-
-	    configurations {
-	    default = "foo-reva.dtb;
-	    foo-reva.dtb {
-		kernel = "kernel";
-		fdt = "fdt-1";
-	    };
-	    foo-revb.dtb {
-		kernel = "kernel";
-		fdt = "fdt-2";
-	    };
-	    foo-reva-bar.dtb {
-		kernel = "kernel";
-		fdt = "fdt-3";
-	    };
-	    foo-revb-bar.dtb {
-		kernel = "kernel";
-		fdt = "fdt-4";
-	    };
-	    foo-revb-baz.dtb {
-		kernel = "kernel";
-		fdt = "fdt-5";
-	    };
-	    foo-revb-bar-baz.dtb {
-		kernel = "kernel";
-		fdt = "fdt-6";
-	    };
-	    };
-	};
+    /dts-v1/;
+    / {
+        images {
+            kernel {
+                data = /incbin/("./zImage");
+                type = "kernel";
+                arch = "arm";
+                os = "linux";
+                load = <0x82000000>;
+                entry = <0x82000000>;
+            };
+            fdt-1 {
+                data = /incbin/("./foo-reva.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+            fdt-2 {
+                data = /incbin/("./foo-revb.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+            fdt-3 {
+                data = /incbin/("./foo-reva-bar.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+            fdt-4 {
+                data = /incbin/("./foo-revb-bar.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+            fdt-5 {
+                data = /incbin/("./foo-revb-baz.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+            fdt-6 {
+                data = /incbin/("./foo-revb-bar-baz.dtb");
+                type = "flat_dt";
+                arch = "arm";
+            };
+        };
+
+        configurations {
+            default = "foo-reva.dtb";
+            foo-reva.dtb {
+                kernel = "kernel";
+                fdt = "fdt-1";
+            };
+            foo-revb.dtb {
+                kernel = "kernel";
+                fdt = "fdt-2";
+            };
+            foo-reva-bar.dtb {
+                kernel = "kernel";
+                fdt = "fdt-3";
+            };
+            foo-revb-bar.dtb {
+                kernel = "kernel";
+                fdt = "fdt-4";
+            };
+            foo-revb-baz.dtb {
+                kernel = "kernel";
+                fdt = "fdt-5";
+            };
+            foo-revb-bar-baz.dtb {
+                kernel = "kernel";
+                fdt = "fdt-6";
+            };
+        };
+    };
 
 Note the blob needs to be compiled for each case and the combinatorial explosion of
 configurations. A typical device tree blob is in the low hundreds of kbytes so a
-- 
2.51.1

[PATCH 9/9] doc: develop: virtio: Fix qemu example (true/false -> on/off)

[Wolfgang Wallner]

The given qemu examples use true/false, while qemu actually on/off.

Signed-off-by: Wolfgang Wallner <wolfgang.wallner@br-automation.com>
---

 doc/develop/driver-model/virtio.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/develop/driver-model/virtio.rst b/doc/develop/driver-model/virtio.rst
index 31b94d04675..9a5e3240c3c 100644
--- a/doc/develop/driver-model/virtio.rst
+++ b/doc/develop/driver-model/virtio.rst
@@ -118,9 +118,9 @@ By default QEMU creates VirtIO legacy devices by default. To create non-legacy
 
   $ qemu-system-i386 -nographic -bios u-boot.rom \
     -netdev tap,ifname=tap0,id=net0 \
-    -device virtio-net-pci,netdev=net0,disable-legacy=true,disable-modern=false \
+    -device virtio-net-pci,netdev=net0,disable-legacy=on,disable-modern=off \
     -drive if=none,file=test.img,format=raw,id=hd0 \
-    -device virtio-blk-pci,drive=hd0,disable-legacy=true,disable-modern=false
+    -device virtio-blk-pci,drive=hd0,disable-legacy=on,disable-modern=off
 
 A 'virtio' command is provided in U-Boot shell.
 
-- 
2.51.1