linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Lapin <slapin@ossfans.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
	"Holger Schurig" <hs4233@mail.mn-solutions.de>,
	linux-wireless@vger.kernel.org,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	maxim.osipov@siemens.com, dmitry.baryshkov@siemens.com,
	oliver.fendt@siemens.com
Subject: Re: Ответ: [PATCH 10/10] ieee802154: add at86rf230/rf231 spi driver
Date: Tue, 2 Jun 2009 12:52:36 +0400	[thread overview]
Message-ID: <20090602085236.GA13088@build.ossfans.org> (raw)
In-Reply-To: <1243931809.3192.68.camel@localhost.localdomain>

On Tue, Jun 02, 2009 at 10:36:49AM +0200, Marcel Holtmann wrote:
> > This gonna happen, as we are most probably going to implement 6lowpan
> > on top of our stack. 6lowpan is a way to encapsulate IPv6 frames into
> > IEEE 802.15.4 and has nothing in common with ZigBee. Moreover
> > ZigBee is a trademark with strict rules upon it's usage. Our lawyers are
> > currently investigating if it's possible to use this name in projects like
> > Linux kernel which are open-source, non-related to any project but
> > OTOH can be encapsulated in any commercial project.
> > 
> > IEEE 802.15.4 is a term like IEEE 802.11. We do have mac80211,
> > we have had (until recently) ieee80211 dir, so why bother?
> > 
> > For Bluetooth naming directories 'bluetooth' is logical, as 802.15.1
> > standard is a less known name, doesn't incorporate latest changes
> > from Bluetooth, etc.
> 
> and so is IEEE 802.15.4 hence we propose using "zigbee" here. Using the
> mac80211 has historical reasons and 802.11 is a known name and even used
> on product marketing material. IEEE 802.15.4 is not. We are also using
> the term "wimax" and not its IEEE numbering.

That WILL add confusion. Because of the following:
1. IEEE 802.15.4 is layer under ZigBee. ZigBee is implemented on top of
IEEE 802.15.4, like UDP is implemented on top of IP.
2. There are hardware implementations of the following sorts:
a) Simple radio (IEEE 802.15.4 PHY).
b) IEEE 802.15.4 MAC
c) ZigBee, or other high level protocols (well, actually I don't know of
any others than ZigBee at this level, but that doesn't mean they don't
exist).

Using this stack we can implement both a) and b). With addition of
ZigBee layers, it might be possible to implement c), too. For things
like 6lowpan, only a) and b) are useful. If you call this all ZigBee,
it will add confusion and artifical limitation. Not to mention, not
true. And just for cosmetic measures. That will be a lot of trouble and
no practical gain from that.

References:
RFC-4919
RFC-4944

All the best,
S.


  parent reply	other threads:[~2009-06-02  9:11 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 14:54 [RFC][WIP] IEEE 802.15.4 implementation for Linux v1 Dmitry Eremin-Solenikov
2009-06-01 14:54 ` [PATCH 01/10] crc-itu-t: add bit-reversed calculation Dmitry Eremin-Solenikov
2009-06-01 14:54   ` [PATCH 02/10] Add constants for the ieee 802.15.4/ZigBee stack Dmitry Eremin-Solenikov
2009-06-01 14:54     ` [PATCH 03/10] net: add IEEE 802.15.4 socket family implementation Dmitry Eremin-Solenikov
2009-06-01 14:54       ` [PATCH 04/10] net: add NL802154 interface for configuration of 802.15.4 devices Dmitry Eremin-Solenikov
2009-06-01 14:54         ` [PATCH 05/10] ieee802154: add simple HardMAC driver sample Dmitry Eremin-Solenikov
2009-06-01 14:54           ` [PATCH 06/10] mac802154: add a software MAC 802.15.4 implementation Dmitry Eremin-Solenikov
2009-06-01 14:54             ` [PATCH 07/10] ieee802154: add virtual loopback driver Dmitry Eremin-Solenikov
2009-06-01 14:54               ` [PATCH 08/10] tty_io: export tty_class Dmitry Eremin-Solenikov
2009-06-01 14:54                 ` [PATCH 09/10] ieee802154: add serial dongle driver Dmitry Eremin-Solenikov
2009-06-01 14:54                   ` [PATCH 10/10] ieee802154: add at86rf230/rf231 spi driver Dmitry Eremin-Solenikov
2009-06-01 16:21                     ` Gábor Stefanik
2009-06-01 20:33                       ` Dmitry Eremin-Solenikov
2009-06-02  8:10                         ` Holger Schurig
2009-06-02  8:21                           ` Marcel Holtmann
2009-06-02  8:29                             ` Ответ: " Dmitry Eremin-Solenikov
2009-06-02  8:36                               ` Marcel Holtmann
2009-06-02  8:46                                 ` Florian Fainelli
2009-06-02  8:49                                 ` Maxim Osipov
2009-06-02  9:15                                   ` Holger Schurig
2009-06-02  9:29                                   ` ?????: " Jonathan Cameron
2009-06-02 11:42                                     ` Dmitry Eremin-Solenikov
2009-06-02  8:52                                 ` Sergey Lapin [this message]
2009-06-01 15:27                   ` [PATCH 09/10] ieee802154: add serial dongle driver Alan Cox
2009-06-01 20:29                     ` Dmitry Eremin-Solenikov
2009-06-01 21:52                       ` Alan Cox
2009-06-02 14:43                         ` Sergey Lapin
2009-06-01 15:07                 ` [PATCH 08/10] tty_io: export tty_class Alan Cox
2009-06-01 15:10                   ` Dmitry Eremin-Solenikov
2009-06-01 15:34                     ` Alan Cox
2009-06-02 14:22                       ` Dmitry Eremin-Solenikov
2009-06-02 14:35                         ` Alan Cox
2009-06-05 12:24             ` [PATCH 06/10] mac802154: add a software MAC 802.15.4 implementation Pavel Machek
2009-06-04  0:32       ` [PATCH 03/10] net: add IEEE 802.15.4 socket family implementation Andrew Morton
2009-06-04 11:16         ` Dmitry Eremin-Solenikov
2009-06-04 13:46           ` John W. Linville
2009-06-04 14:10             ` Dmitry Eremin-Solenikov
2009-06-04 14:15               ` Johannes Berg
2009-06-04  0:05   ` [PATCH 01/10] crc-itu-t: add bit-reversed calculation Andrew Morton
2009-06-05  4:03 ` [RFC][WIP] IEEE 802.15.4 implementation for Linux v1 Jon Smirl
2009-06-05  4:49   ` Dmitry Eremin-Solenikov
2009-06-05 12:58     ` Jon Smirl
2009-06-13  3:21 ` Jon Smirl
2009-06-13  5:37   ` Maxim Osipov
2009-06-13 12:39     ` Jon Smirl
2009-06-21  6:40   ` Pavel Machek

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=20090602085236.GA13088@build.ossfans.org \
    --to=slapin@ossfans.org \
    --cc=dbaryshkov@gmail.com \
    --cc=dmitry.baryshkov@siemens.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxim.osipov@siemens.com \
    --cc=netdev@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    --cc=oliver.fendt@siemens.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;
as well as URLs for NNTP newsgroup(s).