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.) However, you may find that you don't just need to support the latest upstream wpa_supplicant, so ... johannes -- 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
