>If you look at the second row, you'll note that in this case you have to >put the "Location of 160 MHz channel center frequency if BSS bandwidth >is 160 MHz" into CCFS2 (see second-to-last column), so having just this >bit isn't enough. Right, it's not enough, also need to ieee80211_hw_set(hw, SUPPORTS_VHT_EXT_NSS_BW) in driver. ieee80211_chandef_vht_oper() will than set the correct width/center freq. >In fact, I'd argue we need to be able to have the *driver* advertise >this NSS restriction (1/2, 3/4) in the VHT capabilities in nl80211, and >then hostapd build everything according to this table automatically? In order to include this VHT capability in beacons/assoc req, it must be set to hostapd conf file same as other capabilities, such as MAX_MPDU_LENGTH_* for example. What is the alterative ? >Also, we should then have the ability to also set the "Extended NSS BW >Support" field to 2/3, not just 1, and probably then automatically >encode everything according to this table, i.e. setting CCFS2 etc. Agree, if you approve it should be set to hostapd, I will send a new patch to set each bit separately. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any retransmission, dissemination, copying or other use of, or taking of any action in reliance upon this information is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Nothing contained herein shall be deemed as a representation, warranty or a commitment by Celeno. No warranties are expressed or implied, including, but not limited to, any implied warranties of non-infringement, merchantability and fitness for a particular purpose. ________________________________ _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
