From: Alexander Aring <alex.aring@gmail.com>
To: Anoop Kant <Anoop.Kant@LNTTECHSERVICES.COM>
Cc: Vikas Warad <Vikas.Warad@LNTTECHSERVICES.COM>,
Madhu Chinthakindi <Madhu.Chinthakindi@LNTTECHSERVICES.COM>,
"kantanoop@yahoo.com" <kantanoop@yahoo.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: Linux-Wpan-Next: Regarding usage of fakelb driver
Date: Tue, 29 Sep 2015 13:28:20 +0200 [thread overview]
Message-ID: <20150929112815.GA25792@omega> (raw)
In-Reply-To: <51C7DE700DAED543997957503C74C84501074016@POCITMSEXMB05.LntUniverse.com>
On Tue, Sep 29, 2015 at 10:59:52AM +0000, Anoop Kant wrote:
> Dear Alex,
>
> Thanks for quick response!!
>
> I will build image using bluetooth-next git and try.
>
> I believe iwpan and wpan-ping (wpan tools) will already be present in the bluetooth-next-kernel built. Is that correct understanding ?
No, this is part of userspace you need to build it by yourself.
Newest release is 0.5 [0].
It's using autotools as buildsystem so a normal:
./confgure
make
(as root) make install
See [1].
should be enough, we have one dependency to libnl3. See [2], this should
be provided from your distribution which you install. (It's a common
library for networking utilities).
- Alex
[0] http://wpan.cakelab.org/releases/
[1] http://www.gnu.org/software/automake/manual/html_node/Basic-Installation.html#Basic-Installation
[2] http://www.infradead.org/~tgr/libnl (currently the site is down)
next prev parent reply other threads:[~2015-09-29 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51C7DE700DAED543997957503C74C84501073F5A@POCITMSEXMB05.LntUniverse.com>
2015-09-29 10:42 ` Linux-Wpan-Next: Regarding usage of fakelb driver Alexander Aring
2015-09-29 10:59 ` Anoop Kant
2015-09-29 11:28 ` Alexander Aring [this message]
2015-09-30 11:25 ` Anoop Kant
2015-09-30 17:54 ` Alexander Aring
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=20150929112815.GA25792@omega \
--to=alex.aring@gmail.com \
--cc=Anoop.Kant@LNTTECHSERVICES.COM \
--cc=Madhu.Chinthakindi@LNTTECHSERVICES.COM \
--cc=Vikas.Warad@LNTTECHSERVICES.COM \
--cc=kantanoop@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.