Vladimir Kondratiev | 5 Jul 09:24 2015

[PATCH 00/13] wil6210 patches

Several new features introduced:
- TSO improves throughput on Tx side on systems with weak CPU
- ACS chooses best channel automatically when starting AP
- support for the new boot loader

Bug fixes:
- "wait for del_station to complete"
- "hold wil->mutex while managing vrings"

The rest are small fixes and improvements

Dedy Lansky (1):
  wil6210: treat "unhandled event" as warning instead of error

Vladimir Kondratiev (12):
  wil6210: support boot loader struct v0 & v1
  wil6210: ACS implementation using QCA vendor command
  wil6210: debugfs for channel survey
  wil6210: count drops in Rx block ack reorder
  wil6210: print "ulong" fields in hex format in the debugfs
  wil6210: use <> vs. "" for global include
  wil6210: wait for del_station to complete
  wil6210: hold wil->mutex while managing vrings
  wil6210: use wil_fw_error_recovery()
  wil6210: skip HW version check for chip debugging
  wil6210: TSO implementation
  wil6210: improve mgmt frame handling

 drivers/net/wireless/ath/wil6210/boot_loader.h  |  57 ++++
 drivers/net/wireless/ath/wil6210/cfg80211.c     | 389 ++++++++++++++++++++++++
(Continue reading)

sunder | 5 Jul 08:38 2015
Picon

11ac usb dongle MAC80211

Hi,

Is any specific model of USB device with  wlan 11ac  feature and MAC80211 driver ?

Best Regards,

k.sunder  		 	   		  --
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

Zefir Kurtisi | 3 Jul 18:51 2015

Q: iw - how to scan for a specific ssid / AP mode scan

Folks,

I have difficulties using iw for a specific use case or fail to understand the
documentation correctly.

My platform is a recent OpenWRT, running ath9k.

First use case is scanning for a given ssid in managed mode. According do iw's
documentation (and the attribute description in nl80211.h), issuing

iw dev wlan0 scan flush ssid <SSID>

should do exactly this, but I keep receiving a full list of visible APs. I double
checked that NL80211_SCAN_FLAG_FLUSH and NL80211_ATTR_SCAN_SSIDS are set
correctly, so am puzzled whether there is some bug left or I miss some detail.

The second issue is about scanning in AP mode. Where I want to go is having two
APs operating on arbitrary DFS channels with periodic scans to discover each
other. What I observe is
a) passive scanning: iw dev wlan0 scan flush ap-force passive
   => does not work - no scan results are provided
b) active scanning: iw dev wlan0 scan flush ap-force
  * finds only a subset of APs compared to a scan in managed mode
  * finds only APs on non-DFS channels

Again, I might be missing some relevant documentation, but to me the observed
results look rather like 'not yet implemented' than inherent limitations.

Any hint / feedback is appreciated.

(Continue reading)

Lloyds TSB Bank Plc | 29 Jun 14:40 2015
Picon

Darlehen anbieten 1.5%

Guten Tag,

 Dies ist Lloyds TSB Bank plc Kredite anbieten.

   Lloyds TSB bietet flexible und erschwingliche Kredite für jeden Zweck zu helfen, Ihre Ziele zu
erreichen. wir Darlehen zu niedrigen Zinssatz von 1,5%. Hier sind einige wichtige Merkmale der
persönlichen Kredit von Lloyds TSB angeboten. Hier sind die Loan Factors arbeiten wir mit den
führenden britischen Broker, die den Zugang zu Top-Kreditgeber haben und in der Lage, die beste
finanzielle Lösung zu einem erschwinglichen price.Please finden, wenn Sie interessiert sind
kontaktieren Sie uns bitte über diese E-Mail: lloyds25_tsb <at> hotmail.com

Nach der Reaktion, werden Sie einen Antrag auf Kredit fill erhalten. Keine soziale Sicherheit und keine
Bonitätsprüfung, 100% garantiert.

Es wird uns eine Ehre, wenn Sie uns erlauben, zu Ihren Diensten.

Mehr Informationen benötigt

Ihre Namen:
Adresse: ...........
Telefon: ...........
Benötigte Menge: ........
Dauer: ...............
Beruf: ...........
Monatliches Einkommen Level: ........
Geschlecht: ...............
Geburtsdatum: ........
Status: ..................
Land: ..........
Zweck: .........
(Continue reading)

Vasanthakumar Thiagarajan | 3 Jul 15:55 2015

[PATCH] ath10k: Fix target to cpu address conversion logic

'commit 418ca5992e2f ("ath10k: Make target cpu address to
CE address conversion chip specific")' mask 0x7fff is added
by mistake instead of 0x7ff. Fix this regression.

Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@...>
---
 drivers/net/wireless/ath/ath10k/pci.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index 130746b..a69bfa4 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
 <at>  <at>  -765,7 +765,7  <at>  <at>  static u32 ath10k_pci_targ_cpu_to_ce_addr(struct ath10k *ar, u32 addr)
 	case ATH10K_HW_QCA6174:
 		val = (ath10k_pci_read32(ar, SOC_CORE_BASE_ADDRESS +
 					  CORE_CTRL_ADDRESS) &
-		       0x7fff) << 21;
+		       0x7ff) << 21;
 		break;
 	case ATH10K_HW_QCA99X0:
 		val = ath10k_pci_read32(ar, PCIE_BAR_REG_ADDRESS);
--

-- 
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

(Continue reading)

Bartosz Markowski | 3 Jul 15:33 2015

[PATCH] ath10k: fix QCA61X4 boot up

commit "a521ee983d312db7 ath10k: Add new reg_address/mask to hw register
table" commit has broken the QCA61x4 support, by providing wrong
fw_indicator_address, which shall be 0x0003a028 instead of 0x00009028.

User experience was a failing boot up sequence (crashing device during
initialization)

[  181.663874] ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
[  181.664787] ath10k_pci 0000:02:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[  181.688886] ath10k_pci 0000:02:00.0: device has crashed during init
[  181.688897] ath10k_pci 0000:02:00.0: failed to wait for target after cold reset: -70
[  181.688902] ath10k_pci 0000:02:00.0: failed to reset chip: -70
[  181.689774] ath10k_pci: probe of 0000:02:00.0 failed with error -70

Fix it by updating the address with correct value.

Signed-off-by: Bartosz Markowski <bartosz.markowski@...>
---
 drivers/net/wireless/ath/ath10k/hw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/wireless/ath/ath10k/hw.c b/drivers/net/wireless/ath/ath10k/hw.c
index 1414e1f3c7ac..fef7ccf6e185 100644
--- a/drivers/net/wireless/ath/ath10k/hw.c
+++ b/drivers/net/wireless/ath/ath10k/hw.c
 <at>  <at>  -63,7 +63,7  <at>  <at>  const struct ath10k_hw_regs qca6174_regs = {
 	.soc_reset_control_ce_rst_mask		= 0x00000001,
 	.soc_chip_id_address			= 0x000000f0,
 	.scratch_3_address			= 0x00000028,
-	.fw_indicator_address			= 0x00009028,
(Continue reading)

Richard Palethorpe | 3 Jul 11:34 2015

mesh support on rtl8192cu

Hello Taehee,

I have been experimenting with MESH mode on kernel 4.0.7. It is
sending beacons out, but is unable to establish a connection.

I have two rtl8192cu based dongles connected to identical VMs and am
using the following commands to set up the mesh:

iw dev wls160u2 set type mesh
ip addr add 192.168.2.1/24 broadcast 192.168.2.255 dev wls160u2
ip link set wls160u2 up
iw dev wls160u2 mesh join lmmesh

Running 'iw dev wls160u2 mpath dump' produces no results and there is
nothing regarding mesh in dmesg. I can't find any other information on
mesh with rtl8192cu other than the patch which you submitted.

I am wondering if it does work, but there is a step I am missing or if
something is wrong with the code?

Thank you,
Richard.
--
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

miaoqing | 3 Jul 10:28 2015

[PATCH v2] ath9k: export HW random number generator

From: Miaoqing Pan <miaoqing@...>

We measured the ADC-based entropy in 3 ways, Shannon entropy,
collision entropy, and directly measured min-entropy. Entropy is
in bits per 16 bit value,
   ---------------------------
   Shannon | collision | min
   ---------------------------
   12.00   | 10.80     | 9.18
   ---------------------------

Recommend: A generous safety factor be used. NIST Special Publication
800-90B (draft) requires that data used to seed a deterministic random
bit generator with N bits of strength have an estimated entropy at least
twice the block size of the underlying primitive. Given all the
uncertainties, it would be wise to collect even more.

Analysis was done by Jacobson,David(djacobso@...).

Signed-off-by: Miaoqing Pan <miaoqing@...>
---
 drivers/net/wireless/ath/ath9k/Kconfig  |  7 ++++
 drivers/net/wireless/ath/ath9k/Makefile |  1 +
 drivers/net/wireless/ath/ath9k/ath9k.h  | 23 ++++++++++++
 drivers/net/wireless/ath/ath9k/main.c   |  4 ++
 drivers/net/wireless/ath/ath9k/rng.c    | 66 +++++++++++++++++++++++++++++++++
 5 files changed, 101 insertions(+)
 create mode 100644 drivers/net/wireless/ath/ath9k/rng.c

diff --git a/drivers/net/wireless/ath/ath9k/Kconfig b/drivers/net/wireless/ath/ath9k/Kconfig
(Continue reading)

miaoqing | 3 Jul 09:29 2015

[PATCH] ath9k: export HW random number generator

From: Miaoqing Pan <miaoqing@...>

We measured the ADC-based entropy in 3 ways, Shannon entropy,
collision entropy, and directly measured min-entropy. Entropy is
in bits per 16 bit value,
   ---------------------------
   Shannon | collision | min
   ---------------------------
   12.00   | 10.80     | 9.18
   ---------------------------

Recommend: A generous safety factor be used. NIST Special Publication
800-90B (draft) requires that data used to seed a deterministic random
bit generator with N bits of strength have an estimated entropy at least
twice the block size of the underlying primitive. Given all the
uncertainties, it would be wise to collect even more.

Analysis was done by Jacobson,David(djacobso@...).

Signed-off-by: Miaoqing Pan <miaoqing@...>
---
 drivers/net/wireless/ath/ath9k/Kconfig  |  7 ++++
 drivers/net/wireless/ath/ath9k/Makefile |  1 +
 drivers/net/wireless/ath/ath9k/ath9k.h  | 24 +++++++++++
 drivers/net/wireless/ath/ath9k/main.c   |  4 ++
 drivers/net/wireless/ath/ath9k/rng.c    | 73 +++++++++++++++++++++++++++++++++
 5 files changed, 109 insertions(+)
 create mode 100644 drivers/net/wireless/ath/ath9k/rng.c

diff --git a/drivers/net/wireless/ath/ath9k/Kconfig b/drivers/net/wireless/ath/ath9k/Kconfig
(Continue reading)

Vasanthakumar Thiagarajan | 3 Jul 08:15 2015

[PATCH] ath10k: Delay device access after cold reset

It is observed that during cold reset pcie access right
after a write operation to SOC_GLOBAL_RESET_ADDRESS causes
Data Bus Error and system hard lockup. The reason
for bus error is that pcie needs some time to get
back to stable state for any transaction during cold reset. Add
delay of 20 msecs after write of SOC_GLOBAL_RESET_ADDRESS
to fix this issue.

Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@...>
---
 drivers/net/wireless/ath/ath10k/pci.c | 20 +++++++-------------
 1 file changed, 7 insertions(+), 13 deletions(-)

diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index 1b4634a..130746b 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
 <at>  <at>  -2761,7 +2761,6  <at>  <at>  static int ath10k_pci_wait_for_target_init(struct ath10k *ar)

 static int ath10k_pci_cold_reset(struct ath10k *ar)
 {
-	int i;
 	u32 val;

 	ath10k_dbg(ar, ATH10K_DBG_BOOT, "boot cold reset\n");
 <at>  <at>  -2777,23 +2776,18  <at>  <at>  static int ath10k_pci_cold_reset(struct ath10k *ar)
 	val |= 1;
 	ath10k_pci_reg_write32(ar, SOC_GLOBAL_RESET_ADDRESS, val);

-	for (i = 0; i < ATH_PCI_RESET_WAIT_MAX; i++) {
(Continue reading)

David Lin | 3 Jul 08:10 2015

[PATCH v5] Add new mac80211 driver mwlwifi.

The Linux driver for WRT1900AC. The work was initially developed as part of
openwrt effort and maintained on https://github.com/kaloz/mwlwifi.

This is still work in progress, with 8864 chipset more mature and tested,
while 8897 for the similar use case is added recently.

Signed-off-by: David Lin <dlin-eYqpPyKDWXRBDgjK7y7TUQ <at> public.gmane.org>
---
 drivers/net/wireless/Kconfig             |    1 +
 drivers/net/wireless/Makefile            |    2 +
 drivers/net/wireless/mwlwifi/Kconfig     |   24 +
 drivers/net/wireless/mwlwifi/MAINTAINERS |    5 +
 drivers/net/wireless/mwlwifi/Makefile    |   11 +
 drivers/net/wireless/mwlwifi/dev.h       |  435 ++++++
 drivers/net/wireless/mwlwifi/fwcmd.c     | 2278 ++++++++++++++++++++++++++++++
 drivers/net/wireless/mwlwifi/fwcmd.h     |  175 +++
 drivers/net/wireless/mwlwifi/fwdl.c      |  183 +++
 drivers/net/wireless/mwlwifi/fwdl.h      |   27 +
 drivers/net/wireless/mwlwifi/hostcmd.h   |  753 ++++++++++
 drivers/net/wireless/mwlwifi/isr.c       |  148 ++
 drivers/net/wireless/mwlwifi/isr.h       |   26 +
 drivers/net/wireless/mwlwifi/mac80211.c  |  739 ++++++++++
 drivers/net/wireless/mwlwifi/mac80211.h  |   25 +
 drivers/net/wireless/mwlwifi/main.c      |  856 +++++++++++
 drivers/net/wireless/mwlwifi/rx.c        |  519 +++++++
 drivers/net/wireless/mwlwifi/rx.h        |   25 +
 drivers/net/wireless/mwlwifi/sysadpt.h   |   67 +
 drivers/net/wireless/mwlwifi/tx.c        |  834 +++++++++++
 drivers/net/wireless/mwlwifi/tx.h        |   28 +
 21 files changed, 7161 insertions(+)
(Continue reading)


Gmane