On Tue, 2012-06-26 at 15:55 +0200, Michal Kazior wrote: > > I don't think I understand this, wouldn't it need some per-vif requested > > channel type to work correctly? I don't see any chantype values coming > > from the sdata here, so I don't think this could work? > > > > If say vif1 needs ht40+ and vif2 ht20, the channel context will be set > > to ht40+, but then if vif1 goes away and you don't know anything about > > vif2 at all, then how can this work? The way I see it, your code here > > doesn't really do anything, except recalculate that ht40+ is compatible > > with ht40+, or something like that? I guess I'm a bit confused, it seems > > to me that this cannot work even in theory unless you have per-vif data. > > It seems I must've had a mind-derp. I was planning on using > sdata->vif.bss_conf.channel_type which should be ok, right? Yeah, unless you were planning to not go through ieee80211_set_channel_type() any more in the future? 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
