> I am not sure it matters - if I understood your reply, there is no > valid use case to change the frequency in that mode (and all that > code should be removed); All of wext *is* being removed - slowly :) It's not longer default in the kernel configuration now. IIRC, there actually was a valid use case here - to set the frequency before you set the SSID - to be able to force a connection on that channel with wext. > it seems to me that it is also your view that userspace (iwconfig) > should be fixed accordingly to not call the extensions? iwconfig should just be deleted and iw be used :-) > I am just trying to understand how the current code is supposed to > work by exercising widely available user-space tools while debugging > the kernel. Heh, ok. > Actually the frequency gets programmed without errors when reverting > your commit http://tinyurl.com/ho4urp8 (which comes as a surprise as > well). Well, it's not my commit, but that makes sense. I suppose we should treat this as a regression, but reverting that doesn't seem like the right fix. Actually, I'm not convinced we should do monitor channel change anyway when you set the frequency with wext, so we can probably just remove that call there - want to send a patch to that effect? johannes
