I've compiled this experimental USB support and tested with the Linksys WUSB6100 USB adapter (QCA9377). My purpose is for P2P testing (WiFi Display Development). The driver picks up the device and also initialized properly. I am able to broadcast the correct IEs for WFD, however during or immediately after GO negotiation with any device (Nexus 4 and Surface 3 tested) the situation fails and the driver begins multiple log lines of "Received tx completion for invalid msdu_id: 0" . I see a bug in http://lists.infradead.org/pipermail/ath10k/2016-March/006969.html as a possible culprit but am no expert in ath10k. How can I provide more useful feedback?
I've compiled this experimental USB support and tested with the Linksys WUSB6100 USB adapter (QCA9377). My purpose is for P2P testing (WiFi Display Development). The driver picks up the device and also initialized properly. I am able to broadcast the correct IEs for WFD, however during or immediately after GO negotiation with any device (Nexus 4 and Surface 3 tested) the situation fails and the driver begins multiple log lines of "Received tx completion for invalid msdu_id: 0" . I see a bug in http://lists.infradead.org/pipermail/ath10k/2016-March/006969.html as a possible culprit but am no expert in ath10k. How can I provide more useful feedback?