On 08/24/2012 05:35 PM, Johannes Berg wrote:
On Fri, 2012-08-24 at 17:03 +0530, Mahesh Palivela wrote:
/**
* enum ieee80211_chan_width - channel bandwidths
*
* @IEEE80211_CHAN_WIDTH_20MHZ: 20 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_40MHZ: 40 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_80MHZ: 80 MHz chan bandwidth
* @IEEE80211_CHAN_WIDTH_160MHZ: 160 MHz chan bandwidth
*/
We might need 20MHZ_NOHT or something?
Yes, I missed that.
20MHZ_NOHT in 5G band and legacy operation 2.4G band may be 5MHZ.
enum ieee80211_chan_width chan_width2;
u16 control_offset2;
Those shouldn't be necessary, I think? The secondary 80 MHz channel
can't have a control channel, it seems, and the width should be the same
as well? Plus this is only allowed in 80+80 anyway.
johannes
11ac d3.0 spec section 8.4.2.10 says
An operating class for an 80+80 MHz channel bandwidth is expressed by
two consecutive Operating/Sub-
band Sequences, where the first Operating/Subband Sequence field
contains an Operating Triplet for an
80 MHz Channel Spacing with an 80+ Behavior Limit and the second
Operating/Subband Sequence field
contains an Operating Triplet for an 80 MHz Channel Spacing without an
80+ Behavior Limit.
so country might allow primary chan to fall in other frequency segment?
- Mahesh
--
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
