On 20 July 2016 at 13:43, Shajakhan, Mohammed Shafi (Mohammed Shafi) <mohammed@xxxxxxxxxxxxxxxx> wrote: > Michal, > > Can you please let me know if this change is fine or not ? > I am waiting infinitely for your reply long time Sorry. I was absent for a while and this email slipped by. Quoting your other email: > is this patch is good to go (or) should i re-work ? > I had replied to Michal's comment of introducing a new firmware > feature flag will not address the issue in older firmware / code. > Let me know if i had missed something very obvious. I couldn't really find any conclusion to this thread in my inbox. The hw_params approach is definitely wrong. The ACK problem is firmware-specific, not hardware-specific. I'm fine with removing the workaround completely if 636 is guaranteed to not be broken, including AP and P2P GO operation. The client operation will probably work since wmi-roam event is used for HW connection monitoring. Nullfunc tx-status ack/noack reports could be probably fixed up using sta kickout events (with short timeouts) as a fallback. This would make it easier for users because otherwise they'd need to enable disassoc_low_ack in hostapd (which is probably impossible with wpa_supplicant for p2p, no?). Michał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
