From: Alexander Aring <alex.aring@gmail.com>
To: Remi Philippe <remi@linqio.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: 802.15.4G support?
Date: Sun, 28 Feb 2016 15:07:04 +0100 [thread overview]
Message-ID: <20160228140659.GA17980@omega> (raw)
In-Reply-To: <CAH+RWqF-3Q8P52PTM9ZqpybEWTCKiubQK0-Y7L=c-3vAMhJfrg@mail.gmail.com>
Hi,
On Thu, Feb 25, 2016 at 10:22:45PM +0400, Remi Philippe wrote:
> Hello,
>
> We’re currently developing a driver for RF215 (dual radio) using
> 6lowpan and are nearly done with it. We’ve figured out the current MAC
> and PHY are built for 15.4 and not 15.4g which is a blocking point the
> sub-ghz module.
>
ok.
>
> It doesn’t look like there is a need for a huge amount of work to get
> a basic version of it working (key ones we’ve seen are different MTU
> and also some changes in the header like PHR).
>
I took a look into 802.15.4g and you probaly mean with different MTU:
aMaxPHYPacketSize:
2047 for SUN PHYs
127 for all other PHYs
So we working currently with "127" for aMaxPHYPacketSize. In your case you
will have "2047".
Current issue is:
We don't handle this parameter as a variable, it's a define see [0]. :-)
I am fine to change it as variable declaration into PIB [1], then add a
new PHY FLAG [2] for such "SUN PHY's", while registering [3] the phy, it will
update specific constants for such phy's e.g. aMaxPHYPacketSize.
6LoWPAN:
You want to run 6LoWPAN on it, current the 802.15.4 calculates a lot of
stuff with the IEEE802154_MTU define, in most cases when using
fragmentation.
It seems you don't need fragmentation in your case, because you reach
the 1280 minimum MTU for IPv6. The condition at [4] should be always
true then.
Another question would be:
You can run 6LoWPAN on it, but nobody specifies to run 6LoWPAN on such
"SUN PHY's". I actually don't see that. Everything is specified with 127
MTU.
I don't want to tell you cannot run 6LoWPAN on it, but does somebody
need to specify 6LoWPAN for 802.15.4g at first?
>
> Before jumping in coding, is anyone on the list already working on
> this? Or has any starting points.
>
>
I describe one point above for handling different MTU size. I don't know
if somebody already working on 802.15.4g support.
- Alex
[0] http://lxr.free-electrons.com/source/include/linux/ieee802154.h#L29
[1] http://lxr.free-electrons.com/source/include/net/cfg802154.h#L184
[2] http://lxr.free-electrons.com/source/include/net/mac802154.h#L127
[3] http://lxr.free-electrons.com/source/net/mac802154/main.c#L150
[4] http://lxr.free-electrons.com/source/net/ieee802154/6lowpan/tx.c#L285
next prev parent reply other threads:[~2016-02-28 14:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 18:22 802.15.4G support? Remi Philippe
2016-02-28 14:07 ` Alexander Aring [this message]
2016-03-01 9:17 ` Stefan Schmidt
2016-03-03 14:26 ` Michael Richardson
2016-03-04 8:35 ` Alexander Aring
2016-03-04 15:52 ` Michael Richardson
2016-03-04 16:37 ` Alexander Aring
2016-03-04 20:16 ` Michael Richardson
2016-03-14 15:34 ` Stefan Schmidt
2016-03-14 23:11 ` Michael Richardson
2016-03-15 5:19 ` Remi Philippe
2016-03-30 8:54 ` Stefan Schmidt
2016-03-30 17:18 ` Remi Philippe
2016-03-30 21:00 ` Stefan Schmidt
2016-03-04 20:30 ` big frame support in 802.15.4G Michael Richardson
[not found] ` <56DC2A0A.6070906@htt-consult.com>
2016-03-07 16:25 ` [6lo] " Michael Richardson
2016-03-07 16:53 ` Don Sturek
2016-03-07 21:06 ` Robert Moskowitz
2016-03-08 8:22 ` Alexander Aring
[not found] ` <CADrU+dKHiNd2xW0Nd=ZWJCAZQ_PbWXwNFo_V2u4nd7A_ccfwCw@mail.gmail.com>
2016-03-08 14:13 ` Michael Richardson
2016-03-08 14:17 ` Michael Richardson
2016-03-08 14:09 ` Michael Richardson
[not found] ` <CAH+RWqFmxcNxtzTjkcR+Z3dmCdkB5HU-=668rmXMiVaDVZUymg@mail.gmail.com>
2016-03-06 10:17 ` 802.15.4G support? Alexander Aring
2016-03-01 9:15 ` Stefan Schmidt
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=20160228140659.GA17980@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=remi@linqio.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