On 2014-06-13 16:14, Mathy Vanhoef wrote:
[snip]
> Just saw a spelling mistake in the comment, s/Threat/Treat.
One more mistake in the comment.
Change the word "of" to "or":
...underwent a CCK of OFDM reset...
should be
...underwent a CCK or OFDM reset...
Gus
On 14/06/2014 0:07, Felix Fietkau wrote:
> On 2014-06-13 23:41, Mathy Vanhoef wrote:
>> Hi all,
>>
>> This patch allows users to see CCK and OFDM restarts when FIF_FCSFAIL is set.
>> Without this patch only the stronger frame (causing the restart) would be
>> visible.
>>
>> The patch has been teste
On 2014-06-13 23:41, Mathy Vanhoef wrote:
> Hi all,
>
> This patch allows users to see CCK and OFDM restarts when FIF_FCSFAIL is set.
> Without this patch only the stronger frame (causing the restart) would be
> visible.
>
> The patch has been tested using our reactive jammer. The prefix of the w
Hi all,
This patch allows users to see CCK and OFDM restarts when FIF_FCSFAIL is set.
Without this patch only the stronger frame (causing the restart) would be
visible.
The patch has been tested using our reactive jammer. The prefix of the weaker
frame is being correctly passed on as a frame with
Hi all,
Currently ath5k can't report frames with CRC errors. In ath5k_configure_filter
it actually sets the hardware filter properly when the FIF_FCSFAIL flag is set.
However, in other functions the necessary checks weren't being done.
This patch fixes that.
--
From: "Mathy Vanhoef"
When the FI
