[PATCH v2] Documentation: boards: stm32mp: document eMMC partition layout

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

For eMMC, the boot partitions are used for FSBL instead of having
these two partitions in the user area, like with SD-Cards.
Document this.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
  - Fixed missing word in commit message
  - Reworded last paragraph a little
---
 Documentation/boards/stm32mp.rst | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/Documentation/boards/stm32mp.rst b/Documentation/boards/stm32mp.rst
index 6d97b0d6d4a2..de793ab3c96e 100644
--- a/Documentation/boards/stm32mp.rst
+++ b/Documentation/boards/stm32mp.rst
@@ -35,7 +35,7 @@ The resulting images will be placed under ``images/``:
 Flashing barebox
 ----------------
 
-An appropriate image for the boot media can be generated with following
+An appropriate image for a SD-Card can be generated with following
 ``genimage(1)`` config::
 
   image @STM32MP_BOARD@.img {
@@ -61,7 +61,22 @@ An appropriate image for the boot media can be generated with following
       }
   }
 
-Image can then be flashed on e.g. a SD-Card.
+For eMMC, the boot partitions are used as the FSBL partitions and so the user
+partitions may look like this:
+
+  image @STM32MP_BOARD@.img {
+      partition ssbl {
+          image = "barebox-@STM32MP_BOARD@.img"
+          size = 1M
+      }
+      partition barebox-environment {
+          image = "/dev/null"
+          size = 1M
+      }
+  }
+
+The fsbl1 and fsbl2 can be flashed by writing to barebox ``/dev/mmcX.boot0`` and
+``/dev/mmcX.boot1`` respectively or from a booted operating system.
 
 Boot source selection
 ---------------------
-- 
2.25.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox