On Wed, 2009-03-11 at 13:36 +0100, Johannes Berg wrote: > Hi, > > Alina raised an interesting point -- wext allows you to configure an > interface while it is down, at least by convention. Some parameters for > cfg80211 we reject while an interface is down, e.g. adding new stations, > partly for technical reasons and partly because that doesn't make sense > when the mode of interface isn't fixed. > > For cfg80211's assoc/ibss calls, I think we should reject them outright > when the interface is down, any objections? wext *allows* that, but drivers never consistently implemented that (prism54 for example). With most soft-mac style adapters you can't scan while the interface is down either. Anything meaningful use of the interface happens when the firmware (if any) is loaded and the device is operational. The only reason for setting parameters while the device was down was to allow "commit-style" handling of the parameters; set them all up while down, bring the interface up, and it uses all the params you've set/locked on the interface. With cfg80211, that's already handled in a much better manner, thus +1 from me. Dan -- 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
