summaryrefslogtreecommitdiff
path: root/curvetun_mgmt.h
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2016-09-23 09:26:23 +0300
committerTobias Klauser <tklauser@distanz.ch>2016-10-04 17:21:16 +0200
commit5a1eba2843cb66a0cd3b8cccab41d930d7533b62 (patch)
tree6634af085c319939e2680b9129b94d82c93af6be /curvetun_mgmt.h
parentd2801f74136a3b8d7b0f6841d7cb964ebe1d9479 (diff)
trafgen: man: Highlight packet functions section
Make the each packet functions section name to be bold. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'curvetun_mgmt.h')
0 files changed, 0 insertions, 0 deletions
mit an ACK. The problem could be reproduced in a rather busy environment that has a lot of APs. The likelihood could be increased by injecting an msleep() of 5000 or longer immediately after ath10k_htt_setup() in ath10k_core_start(). The reason why the former warnings were only showing up seldom is because the device was either quickly reset again (i.e. during firmware probing) or wmi vdev was created (which fixes hw and fw states). It is technically possible for host driver to override adequate hw registers however this can't work reliably because the bug root cause lies in incorrect firmware state on boot (internal structure used to program MAC_PCU_ADDR1 is not properly initialized) and only vdev create/delete events can fix it. This is why the patch takes dummy vdev approach. This could be fixed in firmware as well but having this fixed in driver is more robust, most notably when thinking of users of older firmware such as 999.999.0.636. Reported-by: Marek Puzyniak <marek.puzyniak@tieto.com> Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat