Ben Greear | 1 Sep 23:29 2015

CT firmware beta-15 can now tune noise-floor thresholds.

Here is the changelog note.  This requires a corresponding driver patch to
enable configuring the firmware.  I tested this on my 4.0.4+ kernel.  I
will be adding this patch to my 3.17 and 4.2 (and future) kernels as well.

Should be useful for anyone trying (and failing) to pass ETSI CCA Adaptivity testing.

You are more likely to cause something to be worse than better, so don't use this
feature unless you know what you are doing and understand the consequences.

This firmware also has some debugging for a case where rate-ctrl gets stuck at
6Mbps and spews lots of dbglog messages into the logs.  This is not easy to
reproduce, but in case someone is debugging such an issue...please send me
full kernel logs if you detect the problem...maybe I can decode them and understand
the problem a bit better now.  You will need to be using my kernel (patches) in order to
get useful firmware logs, by the way.

   *  Enable setting noise-floor-threshold and min-cca-power.  If set, this will over
      ride the defaults, including eeprom (though firmware ignores these settings
      in the eeprom anyway.)  Don't mess with this unless you understand the
      consequences.  But, if set properly, noise-floor-threshold tweaking may fix
      ETSI CCA adapatibility test failures.

http://www.candelatech.com/ath10k.php

Thanks,
Ben

--

-- 
Ben Greear <greearb@...>
Candela Technologies Inc  http://www.candelatech.com
(Continue reading)

Vladimir Kondratiev | 1 Sep 17:24 2015

[PATCH] fixup! wil6210: system power management

Fix compilation warning where CONFIG_PM defined while
CONFIG_PM_SLEEP is not defined

Report follows:

tree:   git://github.com/kvalo/ath pending
head:   941145fc5e5afbb120271e5dfaf37213ddb55807
commit: df596be39294d9712e5d568063a48448031e0a9f [37/39] wil6210: system power management
config: xtensa-allyesconfig (attached as .config)
reproduce:
  wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
  chmod +x ~/bin/make.cross
  git checkout df596be39294d9712e5d568063a48448031e0a9f
  # save the attached .config to linux build tree
  make.cross ARCH=xtensa

All warnings (new ones prefixed by >>):

>> drivers/net/wireless/ath/wil6210/pcie_bus.c:264:12: warning: 'wil6210_suspend' defined but
not used [-Wunused-function]
    static int wil6210_suspend(struct device *dev, bool is_runtime)
               ^
>> drivers/net/wireless/ath/wil6210/pcie_bus.c:291:12: warning: 'wil6210_resume' defined but not
used [-Wunused-function]
    static int wil6210_resume(struct device *dev, bool is_runtime)
               ^
Reported-by: kbuild test robot <fengguang.wu@...>
Signed-off-by: Vladimir Kondratiev <qca_vkondrat@...>
---
 drivers/net/wireless/ath/wil6210/pcie_bus.c | 2 +-
(Continue reading)

Helmut Schaa | 1 Sep 12:12 2015

[RFC 0/2] Send own beacons to monitor interfaces

Sending as RFC to gather some feedback. It can be quite useful
to see own beacons on monitor interfaces for debugging purposes.

However, since there is no tx status for beacons on most drivers
this patchset sends a copy of each beacon fetched via
ieee80211_beacon_get_tim to the monitor interfaces.

Of course, the beacon won't have proper seq numbers for example
as these are filled in in hw/fw.

Still this can be very helpful for debugging.

Helmut Schaa (2):
  mac80211: Split sending tx'ed frames to monitor interfaces into its
    own function
  mac80211: Copy tx'ed beacons to monitor mode

 net/mac80211/ieee80211_i.h |   3 ++
 net/mac80211/status.c      | 108 +++++++++++++++++++++++++--------------------
 net/mac80211/tx.c          |  10 +++++
 3 files changed, 72 insertions(+), 49 deletions(-)

--

-- 
1.8.4.5

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Continue reading)

Rafał Miłecki | 1 Sep 09:55 2015
Picon

[PATCH iw] iw: display interface TX power if available

Signed-off-by: Rafał Miłecki <zajec5@...>
---
This makes use of the recently submitted patch
[PATCH] nl80211: put current TX power in interface info
---
 interface.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/interface.c b/interface.c
index 73ccecd..13806ba 100644
--- a/interface.c
+++ b/interface.c
 <at>  <at>  -367,6 +367,8  <at>  <at>  static int print_iface_handler(struct nl_msg *msg, void *arg)

 		printf("\n");
 	}
+	if (tb_msg[NL80211_ATTR_WIPHY_TX_POWER_LEVEL])
+		printf("%s\ttxpower %d mBm\n", indent, nla_get_u32(tb_msg[NL80211_ATTR_WIPHY_TX_POWER_LEVEL]));

 	return NL_SKIP;
 }
--

-- 
1.8.4.5

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Continue reading)

c_traja | 1 Sep 08:23 2015

[PATCH] ath10k: Disable PCI power save for QCA99X0

From: Tamizh chelvam <c_traja@...>

Frequent failures in waking up the target is observed during
interface (mostly observed with AP and Monitor mode) bring up
on x86, this failures lead to firmware crash. Disabling PCI
power save fixes this issue. Disabling ASPM also does not help,
as a work around disable PCI power save for QCA99X0.

The following kernel log is seen when this issue happens

kworker/dying (667) used greatest stack depth: 12208 bytes left
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x00040050: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a034: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffff81f at 0x0004a034: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xffffffe1 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a42c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a42c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a434: -110
ath10k_pci 0000:07:00.0: firmware crashed! (uuid 40b345f1-db3d-4b97-bc54-6572994e02d5)

Signed-off-by: Tamizh chelvam <c_traja@...>
---
 drivers/net/wireless/ath/ath10k/pci.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index 1046ab6..1ab4ee7 100644
(Continue reading)

miaoqing | 1 Sep 04:56 2015

[PATCH] ath9k: enable hw manual peak calibration for QCA9561

From: Miaoqing Pan <miaoqing@...>

This patch fix https://lists.openwrt.org/pipermail/openwrt-devel/
2015-August/034979.html. As the peak detect calibration is set
incorrectly.

Signed-off-by: Miaoqing Pan <miaoqing@...>
---
 drivers/net/wireless/ath/ath9k/ar9003_calib.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/ar9003_calib.c b/drivers/net/wireless/ath/ath9k/ar9003_calib.c
index 174442b..0c39199 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_calib.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_calib.c
 <at>  <at>  -1249,7 +1249,8  <at>  <at>  static void ar9003_hw_manual_peak_cal(struct ath_hw *ah, u8 chain, bool is_2g)
 		REG_RMW_FIELD(ah, AR_PHY_65NM_RXRF_AGC(chain),
 			      AR_PHY_65NM_RXRF_AGC_AGC2G_CALDAC_OVR, 0x0);

-	if (AR_SREV_9003_PCOEM(ah) || AR_SREV_9550(ah) || AR_SREV_9531(ah)) {
+	if (AR_SREV_9003_PCOEM(ah) || AR_SREV_9550(ah) || AR_SREV_9531(ah) ||
+	    AR_SREV_9561(ah)) {
 		if (is_2g)
 			REG_RMW_FIELD(ah, AR_PHY_65NM_RXRF_AGC(chain),
 				      AR_PHY_65NM_RXRF_AGC_AGC2G_DBDAC_OVR,
 <at>  <at>  -1640,7 +1641,8  <at>  <at>  static bool ar9003_hw_init_cal_soc(struct ath_hw *ah,

 skip_tx_iqcal:
 	if (run_agc_cal || !(ah->ah_flags & AH_FASTCC)) {
-		if (AR_SREV_9330_11(ah) || AR_SREV_9531(ah) || AR_SREV_9550(ah)) {
(Continue reading)

Rafał Miłecki | 31 Aug 22:59 2015
Picon

[PATCH] nl80211: put current TX power in interface info

Many drivers implement reading current TX power (using either cfg80211
or ieee80211 op) but userspace can't get it using nl80211. Right now the
only way to access it is to call some wext ioctl.
Let's put TX power in interface info reply (callback is wdev specific)
just like we do with current channel.
To be consistent (e.g. NL80211_CMD_SET_WIPHY) let's use mBm as na unit.

Signed-off-by: Rafał Miłecki <zajec5@...>
---
 net/wireless/nl80211.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 5d8748b..a5d4e6f 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
 <at>  <at>  -2403,6 +2403,17  <at>  <at>  static int nl80211_send_iface(struct sk_buff *msg, u32 portid, u32 seq, int flag
 		}
 	}

+	if (rdev->ops->get_tx_power) {
+		int dbm, ret;
+
+		ret = rdev_get_tx_power(rdev, wdev, &dbm);
+		if (ret == 0) {
+			if (nla_put_u32(msg, NL80211_ATTR_WIPHY_TX_POWER_LEVEL,
+					DBM_TO_MBM(dbm)))
+				goto nla_put_failure;
+		}
+	}
(Continue reading)

Shengrong Yin | 31 Aug 22:53 2015
Picon

How to set a scan on a given frequency

Hello,

I was using iw to scan a given frequency.
For example,
iw wlan0 scan freq 2412 | grep freq:
However, the result was scanned ssids with different frequencies
across 2.4 GHz band, which is
freq: 2462
freq: 2462
freq: 2437
freq: 2412
...
Why this happened? Shouldn't it return only the ssid with 2412?
I tried to debug iw using ddd. But failed to trace from iw to netlink
library. I traced to
listen_events(state,ARRAY_SIZE(cmds), cmds)
and then I was expected to wait for the scanning result.
The iw tool did only send out the scan request. The netlink library
will handle the scan and call the API provided by mac80211.
Then mac80211 will then request scan from the driver.

Please correct me if I was wrong about the scanning steps.
Should I specify the given frequency for scanning directly in Mac80211?

My goal was to write my own user space process that can handle scan on
a given frequency within a shortest time. But only on one particular frequency.

Thanks,
-Shengrong
--
(Continue reading)

Kuei Hao Liu | 31 Aug 19:53 2015

[PATCH v3] *** Add wmi-tlv support in test mode ***

*** BLURB HERE ***

alanliu (1):
  Add wmi-tlv support in test mode

 drivers/net/wireless/ath/ath10k/core.c     |   4 +-
 drivers/net/wireless/ath/ath10k/core.h     |   5 +-
 drivers/net/wireless/ath/ath10k/testmode.c | 123 ++++++++++++++++++++++++++---
 drivers/net/wireless/ath/ath10k/wmi-tlv.c  |  15 +++-
 4 files changed, 131 insertions(+), 16 deletions(-)

--

-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Kuei Hao Liu | 31 Aug 19:44 2015

[PATCH v3] *** Add wmi-tlv support in test mode ***

*** BLURB HERE ***

alanliu (1):
  Add wmi-tlv support in test mode

 drivers/net/wireless/ath/ath10k/core.c     |   4 +-
 drivers/net/wireless/ath/ath10k/core.h     |   5 +-
 drivers/net/wireless/ath/ath10k/testmode.c | 123 ++++++++++++++++++++++++++---
 drivers/net/wireless/ath/ath10k/wmi-tlv.c  |  15 +++-
 4 files changed, 131 insertions(+), 16 deletions(-)

--

-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

poma | 31 Aug 18:00 2015
Picon

RTL8189ETV


Hi Fi,

What is this device, is it supported by
https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es

$ modinfo rtl8189es
modinfo: ERROR: Module rtl8189es not found.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Gmane