diff options
| author | Michal Kazior <michal.kazior@tieto.com> | 2014-07-21 14:03:10 -0400 |
|---|---|---|
| committer | Kalle Valo <kvalo@qca.qualcomm.com> | 2014-07-22 11:54:04 -0400 |
| commit | c21c64d145e64d92a6c8f8e13c9b6b5b711832eb (patch) | |
| tree | 163134e73641ad5ae1caaa72de832a359c80d4b8 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 4b6045586f31c7cc49b641a7ad5298b0c379a1c7 (diff) | |
ath10k: workaround qos nullfunc bug
Apparently fw/hw generates a corrupted QoS Control
Field in Qos NullFunc frames. The only way to
workaround this is to downgrade frames to
NullFunc. This should be okay since powersave is
done by fw/hw and these frames are only used for
CQM purposes (e.g. from hostapd to check if
station is still connected).
This doesn't fix any user visible bug that I know
of. It just prevents from sending out funky frames
on the air.
Reported-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions