doc: overlay-fdt-boot: .dtbos do not need load addresses

The requirement that .dtbos have load addresses in the FIT image
vanished five years ago with

  4c531d9f58b ("fit: Load DTO into temporary buffer and ignore load address")

Fix the documentation accordingly.

Signed-off-by: Rasmus Villemoes <[email protected]>
Reviewed-by: Marek Vasut <[email protected]>

1 files changed, 1 insertions, 7 deletions

diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst
index 0f012d6988a..5df304047c6 100644
--- a/doc/usage/fit/overlay-fdt-boot.rst
+++ b/doc/usage/fit/overlay-fdt-boot.rst
@@ -141,25 +141,21 @@ explosion problem::
                 data = /incbin/("./reva.dtbo");
                 type = "flat_dt";
                 arch = "arm";
-                load = <0x87fc0000>;
             };
             fdt-3 {
                 data = /incbin/("./revb.dtbo");
                 type = "flat_dt";
                 arch = "arm";
-                load = <0x87fc0000>;
             };
             fdt-4 {
                 data = /incbin/("./bar.dtbo");
                 type = "flat_dt";
                 arch = "arm";
-                load = <0x87fc0000>;
             };
             fdt-5 {
                 data = /incbin/("./baz.dtbo");
                 type = "flat_dt";
                 arch = "arm";
-                load = <0x87fc0000>;
             };
         };
 
@@ -202,9 +198,7 @@ Booting this image is exactly the same as the non-overlay example.
 u-boot will retrieve the base blob and apply the overlays in sequence as
 they are declared in the configuration.
 
-Note the minimum amount of different DT blobs, as well as the requirement for
-the DT blobs to have a load address; the overlay application requires the blobs
-to be writeable.
+Note the minimum amount of different DT blobs.
 
 Configuration using overlays and feature selection
 --------------------------------------------------