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
[email protected]
https://ozlabs.org/mailman/listinfo/devicetree-discuss
_______________________________________________
devicetree-discuss mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/devicetree-discuss
