Argh! My phone doesn't send plain-text emails. Re-adding linux-wpan. I'm not sure what you mean by modified device tree. In the device tree, all I did was add my at86rf212b module as an spi device to the bcm2835-rpi-b-plus.dts. -Rohit On Wed, Jan 21, 2015 at 6:39 PM, Maciej Wasilak <wasilak@xxxxxxxxx> wrote: > Aha - that's very similar situation. I also added u-boot and > bluetooth-next kernel. Are you using modifed device tree? > > 3 months ago I used linux-wpan-next kernel also with Raspbian, and old > userspace tools and everything worked fine. > > Maciek > > 2015-01-21 14:04 GMT+01:00 Rohit Kulkarni <rmkulkar@xxxxxxxxx>: >> I'm using the raspbian distro that came with noobs (from sometime in >> December) and just added u-boot and the bluetooth-next kernel. >> >> -Rohit >> ________________________________ >> From: Maciej Wasilak >> Sent: 21-01-2015 18:13 >> To: Rohit Kulkarni >> >> Subject: Re: Device or resource busy >> >> Hello, >> >> I'm also running bluetooth-next. I replaced normal 3.12 kernel in >> Raspbian with bluetooth-next. Which distro you are using? >> >> Best Regards >> Maciek >> >> 2015-01-21 13:18 GMT+01:00 Rohit Kulkarni <rmkulkar@xxxxxxxxx>: >>> Hi all, >>> >>> I'm now on bluetooth-next and still seeing the problem. So, definitely >>> doesn't look like a raspbian issue. >>> >>> -Rohit >>> ________________________________ >>> From: Maciej Wasilak >>> Sent: 21-01-2015 17:28 >>> To: Rohit Kulkarni >>> Cc: Alexander Aring; linux-wpan@xxxxxxxxxxxxxxx >>> Subject: Re: Device or resource busy >>> >>> Hello >>> >>> 2015-01-21 11:30 GMT+01:00 Rohit Kulkarni <rmkulkar@xxxxxxxxx>: >>>> I tried the "ip link set" command but the wpan interface doesn't go >>>> down. The wpan1 device is already UP on boot and setting the channel >>>> works fine but it fails with -EBUSY when trying to set pan_id. >>> >>> I wrote the previous email about that problem. I experienced same >>> issues as Rohit. It seems that problem doesn't occur on all platforms. >>> Two related questions: >>> >>> 1. Is it possible that this issue is somehow related to distro (we >>> both use Raspbian)? >>> 2. Is it possible that this issue is caused by improper device tree >>> information? Maybe something changed in device tree handling in last 3 >>> months? >>> >>> Best Regards >>> Maciek -- 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
