Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: "Guido Günther" <agx@sigxcpu.org>
To: "Michael C. Cambria" <mcc@fid4.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
	Christoffer Holmstedt <christoffer.holmstedt@gmail.com>,
	linux-wpan@vger.kernel.org
Subject: Re: RPi, Raspbian with openlabs transceiver - lib/tool versions and updated instructions(?)
Date: Wed, 13 May 2015 08:46:44 +0200	[thread overview]
Message-ID: <20150513064644.GA4981@bogon.m.sigxcpu.org> (raw)
In-Reply-To: <554A085D.9050509@fid4.com>

On Wed, May 06, 2015 at 08:26:05AM -0400, Michael C. Cambria wrote:
> 
> 
> On 05/06/2015 05:08 AM, Alexander Aring wrote:
> >On Wed, May 06, 2015 at 09:27:39AM +0200, Christoffer Holmstedt wrote:
> >>I'm currently setting up my dev/test environment to get a "default"
> >>working state to build upon but have stumbled upon some issues on the
> >>way. I'm currently running Raspbian with latest bluetooth-next kernel.
> >>U-Boot from last november. For libnl I use the default packages
> >>available in Raspbian repository. wpan-tools I've checked out the 0.4
> >>release from git repository.
> >>
> >>U-Boot: 2014-11-10 [1]
> >>Raspbian version: 2015-02-16 (originally built with 3.18 kernel)
> >>Bluetooth-next kernel 4.1.0-rc1+ 2015-04-30 [2]
> >>libnl-3-dev version: 3.2.7-4 (Raspbian repository)
> >>libnl-genl-3-dev version: 3.2.7-4 (Raspbian repository)
> >>wpan-tools (tag: wpan-tools-0.4) [3]
> >>
> >>Is this set of libraries/tools ever going to work together or do I
> >>have an obvious mismatch that will for sure fail?
> >>
> >>### command failed: Device or resource busy (-16)
> >I think this is because raspbian has running the ifplug deamon (ifplugd)
> >which do an interface up if you want to do an interface down.
> >
> >Guenther documented this at [0]. Try to do a:
> >
> >kill $(ps awux | grep "[i]fplugd.*wpan0" | awk '{print $2}')
> >
> >into your shell. Then be sure that your interface is down before setting
> >the pan_id.
> 
> I have been able to fix this at boot time by changing /etc/defaults/ifplugd
> 
> From:
> 
> INTERFACES="auto"
> HOTPLUG_INTERFACES="all"
> 
> to:
> 
> INTERFACES="eth0"
> HOTPLUG_INTERFACES="eth0"

I've added a reference to that file to [0], thanks. The reason i left it
out initially is that you have to list interfaces manually then (there's
no EXCLUDE_INTERFACES="wpan*".

Cheers,
 -- Guido

> 
> >Also I saw you have two interfaces and the wpan0 smells like the
> >fakelb(because zero mac address), I currently don't trust the fakelb
> >transceiver. It's a poor driver which should be updated. So in your case
> >you should use the wpan1 interface or remove the fakelb module by
> >putting this module in your blacklist.
> >
> >
> >more background about interface up and address settings:
> >
> >The reason why we doesn't allow this is because if the interface is up
> >and we allow to change the address filter settings in this situation the
> >locking mechanism is a lot of complicated while parsing the frame. To
> >avoid that we simple say "it's a readonly variable when parsing the
> >frame can be occur". The conclusion is we don't need any locking of this
> >variable in a very "strong" context while parsing the frame. If the
> >interface is down, the rtnl mutex is enough to protect this variable.
> >
> >The address filter will be filled when an interface up occurs again then.
> >
> >- Alex
> >

[0] https://honk.sigxcpu.org/piki/hw/rpi6lowpan/

  parent reply	other threads:[~2015-05-13  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  7:27 RPi, Raspbian with openlabs transceiver - lib/tool versions and updated instructions(?) Christoffer Holmstedt
2015-05-06  9:08 ` Alexander Aring
2015-05-06 12:26   ` Michael C. Cambria
2015-05-07  7:37     ` Christoffer Holmstedt
2015-05-13  6:46     ` Guido Günther [this message]
     [not found] ` <5549DA61.2040201@gmail.com>
2015-05-06  9:12   ` Fwd: " Varka Bhadram

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=20150513064644.GA4981@bogon.m.sigxcpu.org \
    --to=agx@sigxcpu.org \
    --cc=alex.aring@gmail.com \
    --cc=christoffer.holmstedt@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mcc@fid4.com \
    /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