So since you felt it was necessary to attack my sanity, let me reply once more. > If mac80211 would have ditched wext and would be using nl80211, I > wouldn't object. But it claims to be wext-compatible, but it > isn't. It is. It isn't compatible to how you expect wext to behave or how some other driver authors wanted wext to behave with their drivers. But since wext never specified how this should work we can rightfully claim wext compatibility. Show documents, comments in the code, anything that backs up your claim. The only thing you've shown so far is stuff that is just as well within spec because spec says nothing and deviates from how we interpret the non-existent spec. > I'm not aware (from those 6) that behaves that way. When I just > enter "iwconfig eth1 essid MUMBLEFUTZ", no key, and then look > at "iwconfig eth1", then I don't see a MAC address of the AP. I'm sure that softmac behaves the way I claimed, so bcm43xx would. > Not "some", but "many" drivers did this, not some. I think > orinoco_cs were used a lot in older days. And madwifi still > get's used a lot. > > Also I have never said that anything is defined here, or please > show me the sentence where I wrote this. I just wrote that > implicitly a number of drivers behave the way. Yes. But what you *are* saying that we should make that the wext specification by requiring everybody else who wants to implement wext to behave that way too. I'm merely questioning that based on the fact that wext doesn't define this and it is *much* easier and nicer to implement it the way we currently do. > 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" johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
