From: Christoffer Holmstedt <christoffer@christofferholmstedt.se>
To: linux-wpan@vger.kernel.org
Subject: 802.15.4 bit- and byte-order
Date: Thu, 25 Jun 2015 11:22:55 +0200 [thread overview]
Message-ID: <20150625092255.GA3682@arazu> (raw)
I remember there were a discussion a few weeks back concerning bit and byte
ordering. I'm not sure if there were any conclusion there but a similiar
discussion just took place on the 6tisch IETF mailing list where they seem to
have come to a conclusion.
I will not copy and paste and try to explain the final conclusion they came to,
that would probably just introduce more questions ;) ...instead I leave you
with a link to the first email in the thread.
https://mailarchive.ietf.org/arch/search/?email_list=6tisch&gbt=1&index=0cQxU9tOmxf5CkPtrULOFyIJbzo
Hope this can help anyone that isn't following that mailing list.
Regards
--
Christoffer Holmstedt
reply other threads:[~2015-06-25 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150625092255.GA3682@arazu \
--to=christoffer@christofferholmstedt.se \
--cc=linux-wpan@vger.kernel.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.