Hi Marcus,
Yes, as I suggested before, you should change it in driver code.
This value in mac80211 codebase is not reflected in ath9k driver(atleast)
where the default is 10 retransmits.
And if someone can explain how does minstrel work with default as 7
retransmits while driver does 10 retransmits
hi all,
I found that there is a retry value in net/wireless/core.c
348 rdev->wiphy.retry_short = 7;
349 rdev->wiphy.retry_long = 4;
If i set those values to 0. the retry will still exist. Is it correct?
Marcus
2014-03-26 21:34 GMT+08:00 abhinav narain :
> Hi,
> just change va
Fejes József wrote:
> I just tried 3.13.9, the problem persists. When I boot back into
> 3.13.5, everything's good again.
>
> Please help. I'd be happy to try patches or provide more information.
You could try a git bisect to find the offending commit between
3.13.5 and 3.13.7.
//Peter
From: Ben Greear
Make sure we cannot ever assign beacon interval to zero.
Signed-off-by: Ben Greear
---
drivers/net/wireless/ath/ath9k/beacon.c | 4
drivers/net/wireless/ath/ath9k/recv.c | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath9
Try looking at the mac80211 layer and in particular net/mac80211/mlme.c.
Check the values of IEEE80211_BEACON_LOSS_COUNT, max_probe_tries, etc.
On Sat, Apr 12, 2014 at 5:37 AM, hong zhang wrote:
> List,
>
> How many beacons a wifi device or AP is allowed to miss?
>
> Some wifi device will disas
Am 15.04.2014 21:42, schrieb Aaron Hamilton:
> Looks like both backports-20140320 and 3.14-1 fail to compile with the
> error ".../backport-include/linux/compat.h:18 error: expected ';', ','
> or ')' before '*' token? Could this be caused by my kernel config?
I can't help you here. take a look at
