> > Face it or not, not everything in life is defined. Nowhere > > is defined how bees behave, and yet they behave in uniform, > > somewhat predicatable ways. So please stop this discussion > > about defined or not defined. mac80211 behaves > > out-of-the-order compared to older drivers. No matter if > > this behavior was formally defined or not. > > It *does* matter because the only thing tools and people using > the tools can rely on is what is defined rather than "happens > to work with driver XY so it must be right" So, things brings me to a weird conclusion: a) earlier you said that in WEXT, the only command that is defined to get you an association is the "iwconfig XXX ap YYY" command. b) you also say that tools should only rely on things that are defined If I accept both sentences as valid, I must conclude that mac80211 is faulty. It happens that mac80211 triggers an association to an access-point also by the "iwconfig XXX essid YYYY" command. This is not defined. Hey, wait a minute. mac80211 is not allowed to do ANYTHING that is undefined, because tools can only rely on defined things. So mac80211 is faulty. Crap, ditch it. I hope you get that somehow this is not only weird, it's unhelpful. Maybe now you can understand why I see thinking in the lines of "only what has defined is right and everything else is wrong" isn't helpful at all. - 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
