From: Michael Richardson <mcr@sandelman.ca>
To: Xue Liu <liuxuenetmail@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCHv2 3/3] ieee802154: Add MCR20A IEEE 802.15.4 device driver
Date: Mon, 19 Feb 2018 12:29:25 -0500 [thread overview]
Message-ID: <23732.1519061365@obiwan.sandelman.ca> (raw)
In-Reply-To: <1519037471-17668-4-git-send-email-liuxuenetmail@gmail.com>
Xue Liu <liuxuenetmail@gmail.com> wrote:
> This driver implements a subset of ieee802154_ops. It has no support
> for CSMA due to lack of hardware support. It has currently no support
> for its proprietary feature: Dual PAN.
I think you mean, that the driver has no support for the MCR20A Dual
Pan feature, because the 802.15.4 layer has no way to deal with it.
A suggestion is to create two virtual devices!
Does the MCR20A support any of the TSCH features?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2018-02-19 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 10:51 [PATCHv2 0/3] ieee802154: Add support for NXP MCR20A Xue Liu
2018-02-19 10:51 ` [PATCHv2 1/3] ieee802154: Add device tree documentation for MCR20A Xue Liu
2018-02-19 10:51 ` [PATCHv2 2/3] ieee802154: Add entry in MAINTAINTERS for MCR20a driver Xue Liu
2018-02-19 10:51 ` [PATCHv2 3/3] ieee802154: Add MCR20A IEEE 802.15.4 device driver Xue Liu
2018-02-19 16:31 ` Stefan Schmidt
2018-02-19 21:40 ` Xue Liu
2018-02-19 22:37 ` Stefan Schmidt
2018-02-19 23:49 ` Xue Liu
2018-02-20 3:44 ` Alexander Aring
2018-02-20 10:42 ` Xue Liu
2018-02-19 23:59 ` Xue Liu
2018-02-20 9:27 ` Stefan Schmidt
2018-02-20 10:45 ` Xue Liu
2018-02-19 17:29 ` Michael Richardson [this message]
2018-02-19 21:42 ` Xue Liu
2018-02-20 3:37 ` Alexander Aring
2018-02-20 10:53 ` Xue Liu
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=23732.1519061365@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=linux-wpan@vger.kernel.org \
--cc=liuxuenetmail@gmail.com \
/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