From: Alexander Aring <alex.aring@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-wpan@vger.kernel.org
Subject: Re: 6lowpan with external radio
Date: Thu, 6 Nov 2014 17:54:27 +0100 [thread overview]
Message-ID: <20141106165425.GA32499@omega> (raw)
In-Reply-To: <CAGnRvuqOcBoDfh899hwB56Hizex7i3q1OasaFJbDBckYiwwPag@mail.gmail.com>
Hi,
On Thu, Nov 06, 2014 at 05:33:51PM +0100, Henning Rogge wrote:
> I had a look at the fakelb driver,
>
> if I understand it right it just "connect" the raw-frame side of
> multiple 6lowpan interfaces with each other, right? So it might be
> part of the solution...
>
> the other part should be similar to the tun.c driver... unfortunately
> the tun driver got quite complex from what I can see.
>
do you use a 802.15.4 radio? Then maybe the serial driver is something
like that what you searching for.
btw. 6LoWPAN is specified for 802.15.4 and btle, maybe there exists also
some other drafts for different L2 layers.
The serial protocol:
There exist a "special" serial protocol v1 and v2.
The serial v2 is only theory concept. v1 is described at [0].
How does it work?
You have some little mcu with an 802.15.4 radio and a special firmware
on it which speaks this protocol via serial bus [0].
On linux side you have a special serial driver [1] which makes an wpan
interface. You can use this driver with any serial device which speaks
this protocol.
Now the big part, this cames never into mainline and I don't want to
accept the current state of driver implementation at [1]. There was also
some subsystem changes. The driver at [1] needs to port to the new
changes. Porting this driver should not be difficult... but there are
also some other parts at this driver why the driver isn't mainlineable.
The idea about a serial driver isn't forgotten but I don't have
currently time to care about that. Have enough to do to keep the
802.15.4 subsystem alive.
- Alex
[0] http://linux-zigbee.sourceforge.net/cgi-bin/trac.cgi/wiki/SerialV1
[1] https://github.com/linux-wpan/linux-wpan-next/commit/546618171de2be30236aab86f3ee323b425e2bf5
next prev parent reply other threads:[~2014-11-06 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 11:14 6lowpan with external radio Henning Rogge
2014-11-06 15:36 ` Marcel Holtmann
2014-11-06 16:33 ` Henning Rogge
2014-11-06 16:54 ` Alexander Aring [this message]
2014-11-06 17:00 ` Henning Rogge
2014-11-06 17:08 ` Alexander Aring
[not found] ` <CAP0sMCzn-cRSDi7GoeLPFKH868vdW+DJsC_ak-eZwT+GEbwwiA@mail.gmail.com>
2014-11-06 18:01 ` Henning Rogge
2014-11-06 18:13 ` Carlo Vallati
2014-11-06 18:28 ` Alexander Aring
2014-11-06 18:24 ` Alexander Aring
2014-11-06 19:34 ` Alexander Aring
2014-11-07 13:22 ` Carlo Vallati
2014-11-06 18:09 ` Carlo Vallati
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=20141106165425.GA32499@omega \
--to=alex.aring@gmail.com \
--cc=hrogge@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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.