All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Laurent Gregoire
	<laurent.gregoire-Jdzig1fPfSTQT0dZR+AlfA@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 07:10:08 -1000	[thread overview]
Message-ID: <499C40F0.5020800@firmworks.com> (raw)
In-Reply-To: <1234975585.17001.131.camel-AlTa8cHOufjkPJRI6LV1/EZjUo8kaGiB@public.gmane.org>

>
> Hi,
>
> We are currently investigating the use of a flattened device-tree for
> configuring some boot parameters on a new ARM platform. ARM being
> little-endian, the first question that arise is whether we should keep
> the .dtb binary format itself big-endian or switch to little-endian?
> Apparently the format does not specify endianness specifically, and I
> did not found any relevant information concerning this.
>   


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.

> Perhaps this has already been decided somewhere on the roadmap of using
> device-tree outside the PPC-world.
>
> Any comments welcomed,
>
> Laurent GREGOIRE
> Embedded Software Engineering | TomTom | www.tomtom.com
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
> https://ozlabs.org/mailman/listinfo/devicetree-discuss
>   

  parent reply	other threads:[~2009-02-18 17:10 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 [this message]
     [not found]     ` <499C40F0.5020800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2009-02-18 18:45       ` Jon Loeliger
     [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=499C40F0.5020800@firmworks.com \
    --to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=laurent.gregoire-Jdzig1fPfSTQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.