On Tue, 2008-10-14 at 23:09 +0200, Michael Buesch wrote: > On Tuesday 14 October 2008 19:49:22 Johannes Berg wrote: > > > > This makes CONFIG_IEEE80211 invisible. The drivers that require it > > (ipw2100, ipw2200, hostap) select it, and everybody else really > > shouldn't even think about using it. Also, since there really is > > no point in compiling anything without crypto support these days, > > remove the crypto options and just enable them, leaving only the > > debugging option which only shows up when a driver is select that > > requires it. This makes it hard to enable, but most people wouldn't > > want to anyway. > > I think in the long term we should also rename it to ipw-ieee80211 > and move it into another directory like drivers/net/wireless/ipw-ieee80211. > This way it's a lot less confusing for new developers joining the wireless developers. True. Also, imho we should reorganise: net/ieee80211/* -> drivers/net/wireless/ipw2x00/* drivers/net/wireless/ipw* -> drivers/net/wireless/ipw2x00/* but as long as the hostap drivers still needs this stuff... > (Probably also rename the symbols. I'm not sure if it's worth it, however) Heh, at least ieee80211_rx would be nice so it doesn't clash with mac80211 any more (though we do have the header file trick which makes ieee80211_rx usable in mac80211 drivers by virtue of being a static inline) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
