On Fri, 2009-10-23 at 09:28 -0700, Dan Williams wrote: > On Fri, 2009-10-23 at 18:04 +0200, Johannes Berg wrote: > > On Fri, 2009-10-23 at 08:49 -0700, Dan Williams wrote: > > > > > > - (iw_handler) lbs_set_freq, /* SIOCSIWFREQ */ > > > > + (iw_handler) cfg80211_wext_siwfreq, > > > > > > > > etc. > > > > > > > > That's why those exist and are exported. And that way you don't need the > > > > Kconfig at all, and can remove most of the wext code. > > > > > > I *think* because Holger is trying to keep WEXT around for a bit, > > > because cfg80211 won't be mature enough yet (IMHO, I could be wrong) by > > > 2.6.33, and because it doesn't support the OLPC-style mesh stuff and the > > > libertas monitor interface code. There's a few loose-ends that need to > > > be tied up before a cfg80211 conversion would completely replace the > > > functionality of the WEXT code. > > > > I just don't understand why he thinks that wext and cfg80211 need to be > > mutually exclusive. cfg80211 has exported its handlers for exactly this > > purpose, so that you could have everything that cfg80211 supports via > > it, and everything else directly. > > I thought about it more, and I think we can go all cfg80211 with a small > WEXT handler for the mesh bits (it only cares about 4 of the WEXT > operations and redirected the rest to the STA interface handlers). The > mesh stuff is actually quite simple operationally. Which should allow us to use cfg80211 by default, and then have only the LIBERTAS_MESH Kconfig option depend on WEXT. Maybe? 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
