linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Evgeniy Eksarevsky <eexarevsky@gmail.com>
Cc: linux-zigbee-devel@lists.sourceforge.net, linux-wpan@vger.kernel.org
Subject: Re: [Linux-zigbee-devel] Linux WPAN sources for ZigBee porting
Date: Thu, 2 Oct 2014 12:29:42 +0200	[thread overview]
Message-ID: <20141002102941.GC19732@omega> (raw)
In-Reply-To: <20141002102717.GB19732@omega>

On Thu, Oct 02, 2014 at 12:27:17PM +0200, Alexander Aring wrote:
> Hi,
> 
> > >
> > >> Just now I am trying to define which MAC features required by ZigBee exist
> > >> and which are missing.
> > >
> > > many.
> > 
> > I know... For now it looks like not using Linux wpan is simpler than use it.
> > 
> 
> correct.
> 
> > >
> > >>
> > >> Which WPAN sources I need to look into?
> > >> Is it official Linux kernel?
> > >> Is it in https://github.com/linux-wpan/linux-wpan-next ?
> > >
> > > Yes it is.
> > >
> > > master: things which should be mainline.
> > > testing: patches for integrating process.
> > 
> > ok, thanks.
> > 
> > >
> > >> Which branch?
> > >>
> > >> Is serial protocol v.2 already implemented?
> > >
> > > No, also v1 isn't mainline.
> > 
> > Yes, I already found a patch for v1.
> > What i definitely need from the serial protocol is ability to do indirect send.
> > 
> 
> indirect send?
> 
> > >
> > >> What do you think about its modification if it will be necessary for
> > >> ZigBee? It will be, for sure...
> > >>
> > >
> > > mac802.15.4 isn't in an useable state. I am currently try to change it
> > > look in the rework branch.
> > 
> > wpan_rework_rfc?
> > 
> 
> Yes, but it's not in a mainline state. I disabled for integrating
> process the 802.15.4 address family. For ZigBee userspace stuff you need
> definitely af802154. I could give you the advice to make everything on
> 802.15.4 RAW sockets. DGRAM sockets are only for data frames and the userspace
> API will be changed eventually.
> 

Okay, netlink interface will definitely be changed in future. Sorry.

- Alex

  reply	other threads:[~2014-10-02 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAdqeRSU=irjdpERicLhZ=cT_cBBfsDEXWeVr7V4z0=OgB2xYw@mail.gmail.com>
     [not found] ` <20141002084013.GA18438@omega>
     [not found]   ` <CAAdqeRQu3-uYVHP-OE7eT839btnf8VmuaEuTr9kx3M_pRMXTWg@mail.gmail.com>
2014-10-02 10:27     ` [Linux-zigbee-devel] Linux WPAN sources for ZigBee porting Alexander Aring
2014-10-02 10:29       ` Alexander Aring [this message]
     [not found]         ` <542EBCD1.8030609@exegin.com>
2014-10-04  3:11           ` Alexander Aring
2014-10-06 17:15             ` Owen Kirby

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=20141002102941.GC19732@omega \
    --to=alex.aring@gmail.com \
    --cc=eexarevsky@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    /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).