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/
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
