On 02/05/2013 07:11 PM, Sascha Herrmann wrote:
>> This is exactly what I meant. There's no reason to store it in the
>> at86rf230_local struct though, since it's only ever used in
>> at86rf230_probe().
>
> Yes, you are right. I will change that and add a comment to platform_data
> field.
>
>
> Whi
Hi,
On Wed, Feb 06, 2013 at 01:11:11AM +0100, Sascha Herrmann wrote:
> > This is exactly what I meant. There's no reason to store it in the
>
> > at86rf230_local struct though, since it's only ever used in
> > at86rf230_probe().
>
>
> Yes, you are right. I will change that and add a comment to
Hi,
forgot to add some information.
On Wed, Feb 06, 2013 at 07:42:27PM +0100, Alexander Aring wrote:
> Hi,
>
> On Wed, Feb 06, 2013 at 01:11:11AM +0100, Sascha Herrmann wrote:
> > > This is exactly what I meant. There's no reason to store it in the
> >
> > > at86rf230_local struct though, since
From: Alexander Aring
Date: Tue, 5 Feb 2013 15:25:35 +0100
> Signed-off-by: Alexander Aring
Applied, thanks.
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and ge
From: Alexander Aring
Date: Tue, 5 Feb 2013 21:23:42 +0100
> In 6lowpan and mac802154 implemenation is a allocated
> temp heap buffer, which can also on the stack.
>
> I hope 100 bytes in 6lowpan are fine.
Series applied to net-next, thanks.
---
Hi,
>> Attaching a scope to the interrupt line, watching the last interrupts
>> before the driver stops working, one can see up to three interrupts for
>> each packet. The first one is the RX_START interrupt, 500us after this
>> the AMI (Adress Match Indication) interrupt is generated and only ab
Hi Alex,
> forgot to add some information.
>>> While the basic function works with this patch for my rpi, I got an
>>> additional problem. When sniffing a ZigBee network the driver stops
>>> working after receiving a random (but small) number of non broadcast
>>> packets.
>>
>> I am working with
