On Sat, Nov 29, 2014 at 12:28 AM, Ben Greear <gree...@candelatech.com> wrote: > I'll investigate the rate-control logic. I don't know enough > about IBSS currently to know why it would use different rate-ctrl logic than > the normal sta/ap, but hopefully I can figure it out. > > Can you post some details on how you configure HT20 v/s legacy mode > for IBSS interfaces?
Alright, this is how I configure adhoc mode. HT20 Mode: iw phy0 interface add wlan0 type adhoc ifconfig wlan0 1.1.1.1 netmask 255.255.255.0 iw wlan0 ibss join adhocnet 5180 HT20 Legacy Mode: iw phy0 interface add wlan0 type adhoc ifconfig wlan0 1.1.1.1 netmask 255.255.255.0 iw wlan0 ibss join adhocnet 5180 By the way, the peer in ath10k is up in legacy mode first before updating the rate to HT20, triggered by drv_sta_rc_update in net/mac80211/ibss.c. Is EEE80211_RC_SUPP_RATES_CHANGED working correctly for ath10k? > > Do you have any reason to believe the problem is in the driver or mac80211 > stack, or is this all a firmware issue? > Rate control is implemented in firmware, right? So it should be firmware issue unless we intended to use the rate control implemented in mac80211 (minstrel). By the way, I haven't done the testing on CT firmware. But as far as I know, for 363 firmware, the setting of higher fixed TX rate is possible if you configure HT20, such as follow: iw wlanX set bitrates legacy-5 ht-mcs-5 3 vht-mcs-5 will setup HT, nss=1, mcs=3 So I think that rate control logic in firmware is not working properly in IBSS mode. > And, if anyone has a different /AC NIC that can do IBSS, I'm curious > if ath10k will receive at higher speeds? > ath9k but the rate control is managed by mac80211. ---- ChunYeow _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
