From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Grant Likely <grant.likely-5wv7dgnIgG8@public.gmane.org>,
daniel.buenzli-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org
Subject: [PATCH] Clarification: dtb size fields are in bytes
Date: Tue, 12 Dec 2017 10:18:00 +0000 [thread overview]
Message-ID: <20171212101800.20853-1-grant.likely@arm.com> (raw)
Clarify that the dtb header totalsize field, and the reserved region
size field specify the size in bytes.
Resolves #9
Signed-off-by: Grant Likely <grant.likely-5wv7dgnIgG8@public.gmane.org>
Cc: daniel.buenzli-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org
---
source/flattened-format.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/source/flattened-format.rst b/source/flattened-format.rst
index a82e502..a1c358e 100644
--- a/source/flattened-format.rst
+++ b/source/flattened-format.rst
@@ -90,8 +90,8 @@ big-endian format.
This field shall contain the value 0xd00dfeed (big-endian).
``totalsize``
- This field shall contain the total size of the devicetree data
- structure. This size shall encompass all sections of the structure:
+ This field shall contain the total size in bytes of the devicetree data structure.
+ This size shall encompass all sections of the structure:
the header, the memory reservation block, structure block and
strings block, as well as any free space gaps between the blocks or
after the final block.
@@ -216,8 +216,8 @@ structure.
uint64_t size;
};
-Each pair gives the physical address and size of a reserved memory
-region. These given regions shall not overlap each other. The list of
+Each pair gives the physical address and size in bytes of a reserved memory region.
+These given regions shall not overlap each other. The list of
reserved blocks shall be terminated with an entry where both address and
size are equal to 0. Note that the address and size values are always
64-bit. On 32-bit CPUs the upper 32-bits of the value are ignored.
--
2.11.0
reply other threads:[~2017-12-12 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171212101800.20853-1-grant.likely@arm.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=daniel.buenzli-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-5wv7dgnIgG8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).