On Tue, 2011-11-08 at 09:25 -0800, Ben Greear wrote: > That's fine by me, I found the code complex as well. All the tmp > and scan and active channel pointers makes for a real mess. Indeed. > But if > you want multiple vifs to work well, then you really need to be able > to continue to function on-channel when some other vif is scanning > on that channel. My use of the wifi stack requires this to work, > so if it takes any significant time to get the new code in I'm going > to have to stick with my complex crap. And I'm not saying you shouldn't, but I think for upstream right now it's not really a good thing. I wish I could say otherwise but given the bugs we have here etc. I don't really feel very confident. Now with multi-channel stuff it's all going to change anyway, each vif will have its own channel and the device will have to mostly sort out the scheduling by itself, ath9k will have to do some tricks in the driver, maybe with some help in mac80211, and off-channel stuff will be interesting too ... johannes -- 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
