From: Jon Loeliger <jdl-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: Of the device tree binary format endianness on little-endian platform
Date: Wed, 18 Feb 2009 12:45:29 -0600 [thread overview]
Message-ID: <499C5749.9000503@freescale.com> (raw)
In-Reply-To: <499C40F0.5020800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
Mitch Bradley wrote:
>
> I can't speak for flattened device trees specifically, but IEEE1275
> (Open Firmware) specifies that integers are encoded in property values
> in big-endian byte order. The model is serialization/deserialization,
> rather than overlaying a C struct on top of the data.
The FDT adopted the same big-endian serialize/deserialize approach.
To be honest, I don't know what motivated the big-endian choice
(Network order, PPC, 1275, One True Format, etc.) Doesn't matter.
jdl
next prev parent reply other threads:[~2009-02-18 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 16:46 Of the device tree binary format endianness on little-endian platform Laurent Gregoire
[not found] ` <1234975585.17001.131.camel-AlTa8cHOufjkPJRI6LV1/EZjUo8kaGiB@public.gmane.org>
2009-02-18 17:10 ` Mitch Bradley
[not found] ` <499C40F0.5020800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-02-18 18:45 ` Jon Loeliger [this message]
[not found] ` <499C5749.9000503-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-02-18 19:01 ` Mitch Bradley
2009-02-18 19:28 ` Of the device tree binary format endianness on little-endianplatform Yoder Stuart-B08248
[not found] ` <9696D7A991D0824DBA8DFAC74A9C5FA304C9D5EA-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2009-02-19 8:54 ` Laurent Gregoire
2009-02-24 21:26 ` Of the device tree binary format endianness on little-endian platform Timur Tabi
[not found] ` <ed82fe3e0902241326g39a5c7fdj861aa37ebe821aee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-25 16:16 ` Laurent Gregoire
[not found] ` <1235578609.17001.318.camel-AlTa8cHOufjkPJRI6LV1/EZjUo8kaGiB@public.gmane.org>
2009-02-26 0:52 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 10:06 Laurent Gregoire
[not found] ` <1235729184.17001.369.camel-AlTa8cHOufjkPJRI6LV1/EZjUo8kaGiB@public.gmane.org>
2009-02-27 10:37 ` David Gibson
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=499C5749.9000503@freescale.com \
--to=jdl-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=wmb-D5eQfiDGL7eakBO8gow8eQ@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 NNTP newsgroup(s).