From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Loeliger Subject: Re: Of the device tree binary format endianness on little-endian platform Date: Wed, 18 Feb 2009 12:45:29 -0600 Message-ID: <499C5749.9000503@freescale.com> References: <1234975585.17001.131.camel@pc-laurentg.intra.local> <499C40F0.5020800@firmworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <499C40F0.5020800-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: Mitch Bradley Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org List-Id: devicetree@vger.kernel.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