netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	slapin@ossfans.org, maxim.osipov@siemens.com,
	dmitry.baryshkov@siemens.com, oliver.fendt@siemens.com
Subject: Re: [RFC][WIP] IEEE 802.15.4 implementation for Linux
Date: Wed, 27 May 2009 16:46:47 +0400	[thread overview]
Message-ID: <bc64b4640905270546k297ee36o4a11f46136863e2b@mail.gmail.com> (raw)
In-Reply-To: <200905271158.57067.florian@openwrt.org>

2009/5/27 Florian Fainelli <florian@openwrt.org>:
> Hi Dmitry,
>
> Le Tuesday 26 May 2009 13:21:57 Dmitry Eremin-Solenikov, vous avez écrit :
>> The project page is available at
>> http://apps.sourceforge.net/trac/linux-zigbee with source code of kernel
>> part available from git at
>> http://zigbee-linux.git.sourceforge.net, mirrored for convenience at
>> git://git.kernel.org/pub/scm/linux/kernel/git/lumag/lowpan.git
>>
>> The source code for userspace utils is available from git at
>> http://linux-zigbee.git.sourceforge.net/
>
> From the project page I understand that you plan on providing a ZigBee stack,
> based on this 802.15.4 stack ? Do you plan on submitting the ZigBee stack
> later on ?

The ZigBee stack currently is in design stage of development. When it will be
more or less "in shape" we will present it to the community.

> Maybe you should mention that this implementation is royalty-free, but that
> commercial products using it should both respect the GPL license and pay a
> ZigBee royalty as per the ZigBee Alliance . That is just for clarification
> since right now it simply does 802.15.4 which is not subject to this royalty
> thing.

We will look into this, thank you for putting our attention on this topic.

>
>>
>> Several comments about our implementation:
>> * As with 802.11 there are two types of devices: the smart ones that
>> implement most parts of the protocol by themselves and more or less dumb
>> ones which simply send and receive what they are told. Currently we do only
>> support the second type of devices (SoftMAC)
>> * The implementation is split between code driving radio, (master, mwpanX
>>   interface: mdev.c), code processing frames according the IEEE 802.15.4
>>   rules (slave wpanX devices) and finally sockets (af_ieee802154.c,
>> dgram.c, raw.c).
>
> This sounds good. Do you also plan on integrating some meshing algorithm on
> top of 802.15.4 ? If so,

Hmmm. IIUC the 802.15.4 doesn't have any knowledge about meshing. It's the
part of higher level protocol. ZigBee part will of course contain some
kind of routing/
meshing algos. If you'd like to implement mesing over raw 802.15.4,
it's up to your
protocol. We plan to provide all hooks necessary for doing this.

>> * We do present two example drivers using our stack. One is purely virtual
>>   one either looping the packets back or connecting several virtual
>> interfaces (the one at fakelb.c), and the driver for the Freescale MC13192
>> evaluation boards (13192-SARD, 13192-EVK) using our custom firmware
>> (currently only available at request, we are working on publishing it). The
>> driver for the Atmel at86rf230/at86rf231 chips will follow in several
>> weeks.
>
> Is the virtual interface just like mac80211_hwsim for 802.11 ?h

More or less.We do not implement the global 'monitor' interface, only separate
radios.  We have a page in the wiki that describes usage of this
virtual device driver:
http://apps.sourceforge.net/trac/linux-zigbee/wiki/GettingStarted

-- 
With best wishes
Dmitry

      reply	other threads:[~2009-05-27 12:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 11:21 [RFC][WIP] IEEE 802.15.4 implementation for Linux Dmitry Eremin-Solenikov
2009-05-26 11:23 ` [PATCH 1/5] Add constants for the ieee 802.15.4/ZigBee stack Dmitry Eremin-Solenikov
2009-05-26 11:23   ` [PATCH 2/5] net: add IEEE 802.15.4 partial implementation Dmitry Eremin-Solenikov
2009-05-26 11:23     ` [PATCH 3/5] ieee802154: add socket address family code Dmitry Eremin-Solenikov
     [not found]       ` <1243336988-20109-3-git-send-email-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-05-26 11:23         ` [PATCH 4/5] ieee802154: add virtual loopback driver Dmitry Eremin-Solenikov
2009-05-26 11:23           ` [PATCH 5/5] ieee802154: add serial dongle driver Dmitry Eremin-Solenikov
     [not found]     ` <1243336988-20109-2-git-send-email-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-05-28  3:08       ` [PATCH 2/5] net: add IEEE 802.15.4 partial implementation Ben Hutchings
2009-05-28  6:35         ` Maxim Osipov
2009-05-28  8:48         ` Dmitry Eremin-Solenikov
2009-05-30 16:32           ` Ben Hutchings
2009-05-27  9:58 ` [RFC][WIP] IEEE 802.15.4 implementation for Linux Florian Fainelli
2009-05-27 12:46   ` Dmitry Eremin-Solenikov [this message]

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=bc64b4640905270546k297ee36o4a11f46136863e2b@mail.gmail.com \
    --to=dbaryshkov@gmail.com \
    --cc=dmitry.baryshkov@siemens.com \
    --cc=florian@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maxim.osipov@siemens.com \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.fendt@siemens.com \
    --cc=slapin@ossfans.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).