qca61x4 uses the vdev param as a sole sufficient configuration
for txbf while qca99x0 enables txbf during peer assoc by
combining the vdev param value with peer assoc's vht capabilities
This patch gets the appropriate txbf configuration scheme
before passing the wmi command to enable the same in
On Mon, Jul 06, 2015 at 10:09:53AM -0700, Wei Zhong wrote:
Related regulation:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6.2.3
Frequency Bands 5470-5600 MHz and 5650-5725 MHz
Until further notice, devices subject to this section [i.e. Wifi device
supporting 5 GHz bands]
A new release of wireless-regdb (master-2015-07-20) is available at:
https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2015.07.20.tar.gz
The short log of changes since the 2015-06-05 release is below.
Thanks,
Seth
---
Seth Forshee (1):
wireless-regdb: update
On 07/19/2015 05:05 PM, Rafał Miłecki wrote:
On 10 July 2015 at 20:31, Arend van Spriel ar...@broadcom.com wrote:
This series comprises of following changes:
- support NVRAM loading for bcm47xx platform.
- revise announced interface combinations and validate against it.
- new debugfs entry for
Hi Dave,
here are few fixes for 4.2, should not have anything out of ordinary.
Please let me know if there are any issues.
Kalle
The following changes since commit 145c37084e3e6584b95f82361922965cc3af41bf:
Doc: z8530book: Fix typo in API-z8530-sync-txdma-open.html (2015-07-10
23:45:31
Janusz Dziedzic janusz.dzied...@tieto.com writes:
In case we will get ROC cancel from mac80211 we
should not call ieee80211_remain_on_channel_expired().
In other case I hit such warning on MIPS and
p2p negotiation failed (tested with use_chanctx=1).
ath: phy0: Starting RoC period
ath:
Now that LSO is working, we can have a big buffer at once
in the driver. Allow to build an A-MSDU out of all this
data. Using A-MSDU will allow better throughput.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/mac80211.c | 1 +
Drivers may be interested in receiving A-MSDU within A-MDPU.
Not all the devices may be able to do so, make it configurable.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
include/net/mac80211.h | 4
net/mac80211/agg-rx.c | 4 +++-
net/mac80211/debugfs.c | 1 +
3 files
A-MSDU is mandatory in the specification, but A-MSDU inside
A-MDPU is not. We need to ensure that the peer is able to
receive an A-MSDU inside an A-MPDU before sending it.
Add the relevant checks.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
Advertise the capability to send A-MSDU within A-MPDU
in the AddBA request sent by mac80211. Let the driver
know about the peer's capabilities.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/dvm/mac80211.c | 2 +-
Since an A-MSDU has one single CRC for the whole
aggregation, it is tricky to know what size to allow.
For now, add a debugfs hook to be able to tune the
algorightm.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/debugfs.c | 19
In VHT, the specification allows to limit the number of
MSDUs in an A-MSDU. Parse the capabilities from the peer
and make them available to the driver.
While at it, add a mask for the A-MSDU length in bytes.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
This implementation is completely software based. Besides
the CSUM, nothing is done in driver.
The driver needs to allocate new skbs, copy and update the
IP / TCP header.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/tx.c | 523
This patch series is really just an RFC: it won't work as
is. I just wanted to share early what we have in the pipe.
We enable TSO to get a lot of data at once to build A-MSDUs.
Our hardware doesn't have (yet) TCP CSUM offload, so we do
it manually. TSO won't be enabled on hardware that don't
From: Johannes Berg johannes.b...@intel.com
Move the TX PN assignment (for CCMP only) to the driver. This prepares
the driver for future DSO (driver segmentation offload) where it will
split an SKB into multiple MPDUs by itself.
For TDLS, split out the CCMP TX command handling so that it won't
In the upcoming patches, iwlmvm will mangle the SKBs if
receives from mac80211, so we can't support
SUPPORTS_CLONED_SKBS anymore.
The next patches introduce support for LSO and the
segmentation will be done while re-using the original SKB
sent by mac80211.
Signed-off-by: Emmanuel Grumbach
I have been looking at an issue with WPA/WPA2 and joining a specific Access
Point SSID that also has a hidden SSID available. This was with 3.14.47 kernel
but it is also present in all 3.x kernels.
When the AP's are being scanned it there is a warning generated stating that
the bssid is empty
HTT_H2T_MSG_TYPE_MGMT_TX msg in 10.4 firmware carries additional
4 byte in htt_mgmt_tx_desc where it tells to firmware that at what
rate mgmt frame has to go out in the air. It's an optional parameter,
setting this field to zero will force firmware to choose auto rate
and send the frame out.
Host memory required for firmware is allocated while handling
wmi service ready event. Right now, wmi service ready is handled
in tasklet context and it calls dma_alloc_coherent() with atomic
flag (GFP_ATOMIC) to allocate memory in host needed for firmware.
The problem is, dma_alloc_coherent()
When max client was set to 512 in qca99x0, there was host memory
alloc failure during wmi service ready event handling. This issue
got resolved now, increasing max client limit from 256 to 512.
Signed-off-by: Raja Mani rm...@qti.qualcomm.com
---
drivers/net/wireless/ath/ath10k/hw.h | 5 +
1
20 matches
Mail list logo
