From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>,
Baptiste Clenet <bapclenet@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: ping6 doesn't use at86rf230 driver
Date: Mon, 29 Jun 2015 14:43:19 +0530 [thread overview]
Message-ID: <55910C2F.3070601@gmail.com> (raw)
In-Reply-To: <20150629080937.GA1674@omega>
On 06/29/2015 01:39 PM, Alexander Aring wrote:
>> Alexander, which version of Linux bluetooth-next tree is based on?
> 4.1.0-rc4-01278-gfbb12f9-dirty
>
> this is currently in my development branch. Alternative you can check
> the Makefile of linux-kernel [0].
>
> VERSION = 4
> PATCHLEVEL = 1
> SUBLEVEL = 0
> EXTRAVERSION = -rc4
> NAME = Hurr durr I'ma sheep
>
>
>
> I really have no idea why you don't have a wpan interface by default.
May be the wpan interface is down :-).
can you please check with: *ifconfig -a*
> You can delete interfaces from nl802154, but then openwrt need to speak
> to this netlink interface and I don't believe that it does that. :-)
Speaking to the netlink interface in OpenWRT is same as in case of bare
Linux kernel compiled for specific target. There is no difference.
So we can use the wpan-tools [1] to speak to the netlink interface.
[1]: http://git.openwrt.org/?p=openwrt.git;a=blob;f=package/network/utils/wpan-tools/Makefile;h=87a5fb1461121407f685e960b64315661aacc9bf;hb=HEAD
--
Varka Bhadram.
next prev parent reply other threads:[~2015-06-29 9:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 16:52 ping6 doesn't use at86rf230 driver Baptiste Clenet
2015-06-25 17:15 ` Alexander Aring
2015-06-25 17:30 ` Alexander Aring
2015-06-26 7:17 ` Baptiste Clenet
2015-06-26 7:20 ` Baptiste Clenet
2015-06-26 8:03 ` Alexander Aring
2015-06-26 8:24 ` Baptiste Clenet
2015-06-29 7:01 ` Baptiste Clenet
2015-06-29 8:09 ` Alexander Aring
2015-06-29 9:13 ` Varka Bhadram [this message]
2015-06-29 9:44 ` Baptiste Clenet
2015-06-29 11:44 ` Baptiste Clenet
2015-06-29 22:09 ` Alexander Aring
2015-06-30 9:12 ` Baptiste Clenet
2015-07-01 8:21 ` Alexander Aring
2015-07-01 9:22 ` Baptiste Clenet
2015-07-01 9:45 ` Baptiste Clenet
2015-07-01 11:59 ` Baptiste Clenet
2015-07-01 15:16 ` Alexander Aring
2015-07-02 15:02 ` Baptiste Clenet
2015-07-02 15:15 ` Baptiste Clenet
2015-07-02 16:12 ` Alexander Aring
2015-07-03 13:24 ` Baptiste Clenet
2015-07-03 13:37 ` Baptiste Clenet
2015-07-03 15:01 ` Baptiste Clenet
2015-07-03 15:47 ` Alexander Aring
2015-07-03 16:33 ` Baptiste Clenet
2015-07-03 17:37 ` Alexander Aring
2015-07-03 22:13 ` Baptiste Clenet
2015-07-04 15:36 ` Alexander Aring
2015-07-05 10:38 ` Baptiste Clenet
2015-07-08 8:35 ` Baptiste Clenet
2015-07-09 11:19 ` Baptiste Clenet
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=55910C2F.3070601@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alex.aring@gmail.com \
--cc=bapclenet@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