So...basically EVERY platform we are dealing with is little-endian,
-- unless you are still running on a 68K (Mac?) of some kind -- but we
force the network types to be big-end just to increase the processing
requirements?
And the full extent of the doc on this is in the T2WG message that
klueska referenced -- which is just a list of things to do?
Actually those are just my usual snotty comments...I should be sorry...
The real question is about the CC2420 header, which in T1.1.15 is still
little-end. Does the radio chip interpret either of the int_16 fields?
Or would it be safe to convert the header to nx_ types as well, just
for consistency?
thanks to everyone who has tried to explain this to me...
MS
Philip Levis wrote:
On Oct 30, 2007, at 10:49 PM, Kevin Klues wrote:
Sorry, you're right, atmeaga128 is little endian as well. The reason
the network types (or more appropriate -- platform independent types)
are needed is because the msp430 expects all tw-byte variables to be
word aligned (can only start at even addresses), while the atmega
allows them to be byte aligned (i.e can start at any address). Making
them network types allows all bytes to be packed consistently on
either platform.
That's one benefit. The other major benefit is that most standardized
protocols are big-endian, so they let you avoid the hton and ntoh
silliness.
Phil
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
