From: Sujay G <sujay.g@hcl.com>
To: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: about openthread and 6lowpan
Date: Sun, 9 Sep 2018 15:05:50 +0000 [thread overview]
Message-ID: <SG2PR04MB315811F19F2A13136294C6A9EF060@SG2PR04MB3158.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <SG2PR04MB3158366EFF8CBC241C84FFD5EF060@SG2PR04MB3158.apcprd04.prod.outlook.com>
Hi,
I have been testing openThread on Docker. I wanted to use 6Lowpan with openthread.
I assumed openThread would interact with wpan interfaces and added wpan interfaces in container namespace but it did not work.
Then I came across change for 6Lowpan. Comparison yielded changes in 7 files vs the latest openThread repositiry
github.com/openthread/openthread/compare/master...linux-wpan:af802154
I manually merged the files and am trying to resolve the errors.
Had few queries regarding the openThread and 6Lowpan
Why was the project (af802154) abandoned ?
Was openThread working with the above 6Lowpan changes ?
Does the current openThread stack support 6Lowpan ? any configuration needs to be enabled ? or is it the right way to port the af802154 to current implementation of openthread ?
-Sujay
::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for
viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
next parent reply other threads:[~2018-09-09 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SG2PR04MB31586E124C6C9A919150F826EF000@SG2PR04MB3158.apcprd04.prod.outlook.com>
[not found] ` <SG2PR04MB3158366EFF8CBC241C84FFD5EF060@SG2PR04MB3158.apcprd04.prod.outlook.com>
2018-09-09 15:05 ` Sujay G [this message]
2018-09-09 20:49 ` about openthread and 6lowpan Michael Richardson
2018-09-10 15:06 ` Alexander Aring
2018-09-20 6:06 ` Sujay G
2018-09-20 6:57 ` Sujay G
2018-09-24 20:56 ` Alexander Aring
2018-09-26 13:28 ` Sujay G
2018-09-26 19:41 ` Alexander Aring
2018-09-24 20:52 ` Alexander Aring
2018-09-10 15:18 ` Alexander Aring
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=SG2PR04MB315811F19F2A13136294C6A9EF060@SG2PR04MB3158.apcprd04.prod.outlook.com \
--to=sujay.g@hcl.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).