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

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

Fix the documentation accordingly.

Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
Reviewed-by: Marek Vasut <marek.vasut@mailbox.org>
This commit is contained in:
Rasmus Villemoes
2026-03-17 14:13:36 +01:00
committed by Heinrich Schuchardt
parent 22037a6ebb
commit c009771427

View File

@@ -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
--------------------------------------------------