summaryrefslogtreecommitdiff
path: root/doc/board
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2026-03-09 15:26:34 -0600
committerTom Rini <[email protected]>2026-03-09 15:26:34 -0600
commit1e240f7206fccde4ec73ea432ab8360d321c5fe5 (patch)
tree931d5985e8a237b5604999922f5662fc464a8817 /doc/board
parent36add050eea439f0b2a15e4ea0d3a8e21216f159 (diff)
parentba7bf918dafcd093ad733b07ba490baeb20cf5da (diff)
Merge tag 'v2026.04-rc4' into next
Prepare v2026.04-rc4
Diffstat (limited to 'doc/board')
-rw-r--r--doc/board/samsung/exynos-mobile.rst5
-rw-r--r--doc/board/samsung/exynos-mobile/exynos7870.rst42
2 files changed, 7 insertions, 40 deletions
diff --git a/doc/board/samsung/exynos-mobile.rst b/doc/board/samsung/exynos-mobile.rst
index 37718af1fea..d0173b1f8cb 100644
--- a/doc/board/samsung/exynos-mobile.rst
+++ b/doc/board/samsung/exynos-mobile.rst
@@ -25,12 +25,13 @@ If a cross-compiler is required, install it and set it up like so:
export CROSS_COMPILE=aarch64-linux-gnu-
-Then, run the following commands to build U-Boot:
+Then, run the following commands to build U-Boot (replace ``<dtb>`` with the
+upstream DTB path for the target device):
.. prompt:: bash $
make O=.output exynos-mobile_defconfig
- make O=.output -j$(nproc)
+ make DEVICE_TREE=<dtb> O=.output -j$(nproc)
If successful, the U-Boot binary will be present in ``.output/u-boot.bin``.
diff --git a/doc/board/samsung/exynos-mobile/exynos7870.rst b/doc/board/samsung/exynos-mobile/exynos7870.rst
index bbd857580b8..702b21244eb 100644
--- a/doc/board/samsung/exynos-mobile/exynos7870.rst
+++ b/doc/board/samsung/exynos-mobile/exynos7870.rst
@@ -6,54 +6,20 @@ Samsung Exynos 7870 Boards
Preparation
-----------
-Create the following device tree (named ``stub.dts``)
-.. code-block:: devicetree
-
- /dts-v1/;
-
- / {
- compatible = "samsung,exynos7870";
- #address-cells = <2>;
- #size-cells = <1>;
-
- model_info-chip = <7870>;
- model_info-hw_rev = <0>;
- model_info-hw_rev_end = <255>;
-
- chosen {
- };
-
- memory@80000000 {
- device_type = "memory";
- reg = <0x0 0x80000000 0x0>;
- };
-
- memory@100000000 {
- device_type = "memory";
- reg = <0x1 0x00000000 0x0>;
- };
- };
-
-The chosen node and memory ranges are populated by S-BOOT. A certain device
-model may have multiple variants, with differing amounts of RAM and storage. The
-RAM capacity information is graciously provided by S-BOOT's device tree
-overlays.
-
-Compile it to a device tree blob, then pack it in the QCDT format [1]_ using
-``dtbTool-exynos`` [2]_ by issuing the following commands:
+Pack the device tree blob in the QCDT format [1]_ using ``dtbTool-exynos`` [2]_
+by issuing the following commands:
.. prompt:: bash $
- dtc -I dts -O dtb -o stub.dtb stub.dts
- dtbTool-exynos -o stub-dt.img stub.dtb
+ dtbTool-exynos -o stub-dt.img .output/u-boot.dtb
Finally, use ``mkbootimg`` by osm0sis [3]_ to generate the boot image:
.. prompt:: bash $
mkbootimg -o u-boot.img \
- --kernel .output/u-boot.bin \
+ --kernel .output/u-boot-nodtb.bin \
--dt stub-dt.img
Offsets are not provided to ``mkbootimg`` as S-BOOT ignores them.