On 02/10/2014 09:12 AM, Johannes Berg wrote: > On Sat, 2014-02-08 at 10:42 +0100, Arend van Spriel wrote: >> On 02/03/14 21:39, Emmanuel Grumbach wrote: >>> From: Johannes Berg<johannes.berg@xxxxxxxxx> >>> >>> The iwlwifi scheduled scan implementation doesn't adhere to the >>> userspace API correctly - the API assumes that any new incoming >>> 'incompatible' request (like scan or remain-on-channel for this >>> driver) will just cancel the scheduled scan. Instead our driver >>> relies on userspace cancelling it, thus breaking existing wpa_s >>> versions. >> >> I think iwlwifi is not alone in this. At least I have to put a new task >> on my todo list ;-) > > :) > You may decide to not care - newer supplicant seems to always cancel > scheduled scan first (although that should never have been required, > Broadcom's proprietary Android driver also behaves to require that.) When implementing scheduled scan, I found our firmware can handle a regular scan regardless whether a scheduled scan is active or not. > However, you may find that you don't just need to support the latest > upstream wpa_supplicant, so ... Yeah, seems to happen more often than not. Also when people start using backports they are advised to upgrade user-space apps as well, but tend to stick to what the distro has, so ... > johannes Arend -- 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
