On Tue, 2012-07-24 at 16:18 +0530, Mahesh Palivela wrote: > >> indicating the number of channels below/above control (for control > >> channel 1,2,3,4 respectively). Similarly, for VHT160 you'd have 8 > >> possibilities: > >> > >> |-1-|-2-|-3-|-4-|-5-|-6-|-7-|-8-| > >> > >> (which one could again capture as VHT_CHAN_LAYOUT_0_7 etc.) > >> > >> [MP] I see your point. But according to 11ac spec, AP will use primary > >> chan as specified in HT operation IE chan num. Secondary channel is > >> center freq specified in VHT Operation IE. So I am thinking secondary > >> channel is not relative offset to primary channel. Hope I am not > >> mistaken here. > > > > Ok so HT has primary channel and secondary, and VHT has secondary VHT > > which can again be above/below? That would make sense, but you wouldn't > > be covering it. > > > > I am thinking no need of above/below convention as the center frequency > value itself we know. But we don't use the center frequency of the overall Ht40/80/160 channel, we always use the center frequency of the control channel. > >>> + /* This would happen when regulatory rules disallow VHT80 completely */ > >>> + if (IEEE80211_CHAN_NO_VHT80 == (chan->flags & (IEEE80211_CHAN_NO_VHT80))) > >>> + return true; > >> > >> Is that really right? Need to document what the return value of this > >> function should be, I guess? > >> > >> [MP] I guess, it's possible for a channel not allowed for 80Mhz operation. > > > > Yeah but should it really check *all* the bits rather than any one of > > them? > > > > You mean to say other bits like HT40MINUS, HT40PLUS or even DFS? No, I mean all the bits that are part of CHAN_NO_VHT80. 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
