From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Subject: new netlink interface cfg802154
Date: Tue, 19 Aug 2014 12:06:45 +0200 [thread overview]
Message-ID: <20140819100643.GB827@omega> (raw)
Hi,
I will send in the next days a new implementation for the netlink
interface.
Why?
I don't know where I can begin to say what's wrong with the current
netlink interface. It has some half implemented features and the
userspace header (they are not in uapi) contains "extern ..." things for
the policy.
Right now the lowpan-tools supports add/del interfaces and setting of
hardware filter functionality, pan_id, short_address, nothing more.
There are some other userspace application (I know two) which talk
with this interface. Please don't be angry that you need to updated
the userspace application according the new one.
The new interface is like cfg80211, but with 802.15.4 functionality. I
begun to make everything like the wirless stack and then we can think
about bringing 802.15.4 functionality into this stack.
Also I implemented a new userspace tool package "wpan-tools" [0].
This will contain the iwpan tool. This code is mostly based on the iw
tool from wireless [1]. It currently support adding new interface and
delete exist interfaces. It's very modular and we can easy add new
netlink features.
The nl802154.h should not updated in the wpan-tools, it should updated
on the kernel side.
I will send the cfg802154 patches to this mailinglist, when I get basic
support for channel and pan id setting.
- Alex
[0] https://github.com/linux-wpan/wpan-tools
[1] http://git.kernel.org/cgit/linux/kernel/git/jberg/iw.git
reply other threads:[~2014-08-19 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140819100643.GB827@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.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