[Linux-zigbee-devel] [PATCH] at86rf230: we may be in BUSY_RX after commanding RX_ON

2011-07-07 Thread Werner Almesberger
Checking arrival in RX_ON races with incoming traffic. If frame reception begins before we have a chance to see that we've arrived in RX_ON, at86rf230_state complains about unexpectedly finding the transceiver in BUSY_RX. This isn't the prettiest solution (and it doesn't check if we're in BUSY_RX

Re: [Linux-zigbee-devel] [PATCH] at86rf230: we may be in BUSY_RX after commanding RX_ON

2011-07-07 Thread Alexander Smirnov
Sorry, forgot CC: linux-zigbee-devel@lists.sourceforge.net Hi Werner, thank you for your another patch! Currently I don't clearly imagine a situation, when in BUSY_RX condition we will request for RX_ON. As I see, request for RX_ON provided only by at86rf230_start function. It's called in xmit o

Re: [Linux-zigbee-devel] [PATCH] at86rf230: we may be in BUSY_RX after commanding RX_ON

2011-07-07 Thread Werner Almesberger
Ah, you sent this separately in private mail and to the list. Here's my reply also for the list: Alexander Smirnov wrote: > Currently I don't clearly imagine a situation, when in BUSY_RX condition > we will request for RX_ON. Sorry, my description may have been a bit fuzzy. This happens after at8