summaryrefslogtreecommitdiffstats
path: root/sys/contrib/dev
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2015-10-10 00:13:45 +0000
committeradrian <adrian@FreeBSD.org>2015-10-10 00:13:45 +0000
commit8d135240735275b0d2f31b6fdc119fb32ac79117 (patch)
treea4e8cf35471c0d2a215577b061df1c097f5e26b5 /sys/contrib/dev
parent01da20b0383d8d3526490eee4524441d366f3aa1 (diff)
downloadFreeBSD-src-8d135240735275b0d2f31b6fdc119fb32ac79117.zip
FreeBSD-src-8d135240735275b0d2f31b6fdc119fb32ac79117.tar.gz
Flip on fast frames support for AR5416 and AR9300 series NICs.
This was off because the net80211 aggregation code was using the same state pointers for both fast frames and ampdu tx support which led to some pretty unfortunate panic-y behaviour. Now that net80211 doesn't panic, let's flip this back on. It doesn't (yet) do the horrific sounding thing of A-MPDU aggregates of fast frames; that'll come next. It's a pre-requisite to supporting AMSDU + AMPDU anyway, which actually speeds things up quite considerably (think packing lots of little ACK frames into a single AMSDU.) Tested: * QCA955x SoC, AP mode * AR5416, STA mode * AR9170, STA mode (with local fast frame patches)
Diffstat (limited to 'sys/contrib/dev')
-rw-r--r--sys/contrib/dev/ath/ath_hal/ar9300/ar9300_attach.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_attach.c b/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_attach.c
index a446f96..adbef28 100644
--- a/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_attach.c
+++ b/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_attach.c
@@ -2671,7 +2671,7 @@ ar9300_fill_capability_info(struct ath_hal *ah)
p_cap->halBurstSupport = AH_TRUE;
p_cap->halChapTuningSupport = AH_TRUE;
p_cap->halTurboPrimeSupport = AH_TRUE;
- p_cap->halFastFramesSupport = AH_FALSE;
+ p_cap->halFastFramesSupport = AH_TRUE;
p_cap->halTurboGSupport = p_cap->halWirelessModes & HAL_MODE_108G;
OpenPOWER on IntegriCloud