wrote:
> 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...
>
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
>>
with bad CRC!
--
From: "Mathy Vanhoef"
Treat frames that underwent a CCK or OFDM restart as frames with an invalid CRC.
Signed-off-by: Mathy Vanhoef
---
drivers/net/wireless/ath/ath5k/base.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wi
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 Vanh
g / adding
something.
For a quick introduction to the wireless stack on Linux:
http://au-kbc.org/comm/Docs/papers/Vipin_Analysis_of_open_source_WLAN_driver_paper.pdf
- Mathy
On Mon, Feb 17, 2014 at 10:27 AM, Holger Schurig wrote:
> Okay, I admit that I cannot help you, I have no clue on the
might
indicate where the problem is, or hopefully give you new ideas to fix the
problem.
- Mathy
On Mon, Feb 17, 2014 at 6:41 PM, abhinav narain
wrote:
> Hi,
> There is a AR5K_DIAG_SW_5211 register in ath5k codebase (in reg.h) .
> I am using AR5212 NIC and even if I set all the bits
fully convinced of the experiments/arguments these papers
give, and unfortunately I don't have these chipsets to experiment
myself. However, when experimenting with an AR7010 and AR9271, I did
not observe the message in message mode support.
Cheers,
Mathy
[1] Order Matters: Transmission Reordering i
