On Fri, 2014-05-23 at 05:38 +0300, Luca Coelho wrote: > From: Luciano Coelho <luciano.coelho@xxxxxxxxx> > > In some cases, when the driver is already using all the channel > contexts it can handle at once, we have to do an in-place switch > (ie. we cannot afford using an extra context temporarily for the > transaction). But some drivers may not support switching the channel > context assigned to a vif on the fly (ie. without unassigning and > assigning it) while others may only work if the context is changed on > the fly, without unassigning it first. > > To allow these different scenarios, add a new driver operation that > let's the driver decide how to handle an in-place switch. > > Additionally, remove the IEEE80211_HW_CHANGE_RUNNING_CHANCTX flag, > since we never change a running context directly anymore. > > Signed-off-by: Luciano Coelho <luciano.coelho@xxxxxxxxx> > --- So, this is what I had cooked up. Sorry Michal, I should have synced with you. Actually I tried to ping you on IRC, but you were not there, and then I forgot to sync by email. In any case, our patches were very similar, since the whole API discussion had already been done before. Some details are different though, and my version only supports a single vif (obviously). Also, I already added a usage of the new op in a new ieee80211_vif_change_reserved_context() function (which is similar to Michal's "change incopat" function). -- Luca. -- 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
