summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKrystian Hebel <krystian.hebel@3mdeb.com>2021-05-28 12:51:18 +0200
committerPatrick Georgi <pgeorgi@google.com>2021-06-11 07:41:59 +0000
commitdee3bc34ad3be944390369724a46ecf01398c51a (patch)
tree004d3b492cc9ca77064efc43d0e6695ab4412530
parent3c75a8db35957bd501dfa2443f2e0a74d88c0a3f (diff)
docs/flashmap: state the endianness of FMAP
Signed-off-by: Krystian Hebel <krystian.hebel@3mdeb.com> Change-Id: Idf6d46ed262b18c176d69352e333c56f4fdff66a Reviewed-on: https://review.coreboot.org/c/coreboot/+/55041 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com>
-rw-r--r--Documentation/lib/flashmap.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/lib/flashmap.md b/Documentation/lib/flashmap.md
index d3d8bbf6ea..68d0ab5dc7 100644
--- a/Documentation/lib/flashmap.md
+++ b/Documentation/lib/flashmap.md
@@ -17,7 +17,8 @@ something else) should have its own Flashmap section, and everything else should
normally go into CBFS.
The Flashmap itself starts with a header `struct fmap` and followed by a list of
-section descriptions in `struct fmap_area`.
+section descriptions in `struct fmap_area`. All fields in those structures are
+in little endian format.
### Header
The header `struct fmap` has following fields: