From: Alexander Aring <alex.aring@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: 6lowpan on a RPi using at86rf233
Date: Fri, 3 Apr 2015 16:45:02 +0200 [thread overview]
Message-ID: <20150403144459.GA773@omega> (raw)
In-Reply-To: <20150403143647.GA6266@bogon.m.sigxcpu.org>
On Fri, Apr 03, 2015 at 04:36:47PM +0200, Guido Günther wrote:
> Hi,
> I'm trying to get 6lowpan to work using bluetooth-next on the above
> hardware[1]. I'm currently using bluetooth-next as of
> baf880a96859cca79208122e555e7efeabd16e4d . When I do a:
>
> iwpan dev wpan0 set pan_id 0xbeef
>
> I get:
>
> command failed: Device or resource busy (-16)
>
you can set the pan_id when you interface is down only.
> or in detail:
>
> # src/iwpan --debug dev wpan0 set pan_id 0xbeef
> -- Debug: Sent Message:
> -------------------------- BEGIN NETLINK MESSAGE ---------------------------
> [HEADER] 16 octets
> .nlmsg_len = 36
> .nlmsg_type = 21 <0x15>
> .nlmsg_flags = 5 <REQUEST,ACK>
> .nlmsg_seq = 1428071645
> .nlmsg_pid = 2760
> [PAYLOAD] 20 octets
> 0a 00 00 00 08 00 03 00 05 00 00 00 06 00 09 00 ef be ..................
> 00 00 ..
> --------------------------- END NETLINK MESSAGE ---------------------------
> -- Debug: Received Message:
> -------------------------- BEGIN NETLINK MESSAGE ---------------------------
> [HEADER] 16 octets
> .nlmsg_len = 56
> .nlmsg_type = 2 <ERROR>
> .nlmsg_flags = 0 <>
> .nlmsg_seq = 1428071645
> .nlmsg_pid = 2760
> [ERRORMSG] 20 octets
> .error = -16 "Device or resource busy"
> [ORIGINAL MESSAGE] 16 octets
> .nlmsg_len = 16
> .nlmsg_type = 21 <0x15>
> .nlmsg_flags = 5 <REQUEST,ACK>
> .nlmsg_seq = 1428071645
> .nlmsg_pid = 2760
> --------------------------- END NETLINK MESSAGE ---------------------------
>
> This looks similar to
>
> http://www.spinics.net/lists/linux-wpan/msg01290.html
>
> but I'm running wpan-tools master already.
>
> Before digging deeper it'd be great to know if these version should work together or if
> another kernel tree should be used otherwise I'll sprink some pr_debugs().
> Cheers,
> -- Guido
>
> [1] https://honk.sigxcpu.org/piki/hw/rpi6lowpan/
- Alex
next parent reply other threads:[~2015-04-03 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150403143647.GA6266@bogon.m.sigxcpu.org>
2015-04-03 14:45 ` Alexander Aring [this message]
2015-04-03 18:27 ` 6lowpan on a RPi using at86rf233 Guido Günther
2015-04-03 18:38 ` Alexander Aring
2015-04-07 11:49 ` Guido Günther
2015-04-07 19:07 ` Alexander Aring
2015-04-09 9:06 ` Guido Günther
2015-04-09 10:21 ` Alexander Aring
2015-04-03 18:49 ` 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=20150403144459.GA773@omega \
--to=alex.aring@gmail.com \
--cc=agx@sigxcpu.org \
--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