On Fri, 2009-10-23 at 18:39 +0200, Johannes Berg wrote: > On Fri, 2009-10-23 at 09:31 -0700, Dan Williams wrote: > > > > > 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? > > Well if you want to push the mesh wext bits through to cfg80211 > (temporarily) you wouldn't even need to depend on WEXT. I'd prefer, > however, to not do this, and just use the cfg80211 wext handlers in > libertas and depend on WEXT for now. Yeah, I think it's best to handle the mesh WEXT ioctls separately for now. There are really only 4 of them (get/set SSID, set channel, get mode) that matter for mesh. The rest of the ioctls that the mesh interface supports get redirected to the cfg80211 handlers because they aren't specific to mesh. 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
