..hello...

2014-11-23 Thread hi
Samsung S5 270 euro, iphone 6plus, 430euro , ipad, ... si te :assr . conN�Р骒r��yb�X�肚�v�^�)藓{.n�+�伐�{甭*���,�{ay��,j��f"�h���z��wア� ⒎�j:+v���w�j�m��赙zZ+�茛j"��!�i

Re: Fwd: Linux kernel 3.12 PN-KEY Mismatch in wpa.c, packet drop

2014-11-23 Thread deepak kumar Pradhan
Thank you Johannes for your response. Since we were facing this issue, i looked at the available patches. None solved the issue for us. I may be missing something, can you please let me know if the solution for this is already available? Any inputs much appreciated. regards On Fri, Nov 21, 2014 a

[PATCH 2/3] ath10k: Fix locking for WEP keys

2014-11-23 Thread Sujith Manoharan
From: Sujith Manoharan peer->keys needs to be protected by data_lock since it is also accessed from the WMI path. Both install() and clear() routines for peer keys modify the key contents, so use the data_lock to avoid races. Signed-off-by: Sujith Manoharan --- drivers/net/wireless/ath/ath10k

[PATCH 0/3] ath10k patches

2014-11-23 Thread Sujith Manoharan
From: Sujith Manoharan Fixes for WEP. Sujith Manoharan (3): ath10k: Fix shared WEP ath10k: Fix locking for WEP keys ath10k: Fix bug reported by lockdep drivers/net/wireless/ath/ath10k/mac.c | 31 +-- drivers/net/wireless/ath/ath10k/mac.h | 2 ++ drivers/net/w

[PATCH 3/3] ath10k: Fix bug reported by lockdep

2014-11-23 Thread Sujith Manoharan
From: Sujith Manoharan ath10k_tx_wep_key_work() acquires conf_mutex, so cancelling it when conf_mutex is already taken in ath10k_remove_interface() is incorrect, so move it outside the lock. Snippet from the lockdep report: kernel: == kernel:

[PATCH 1/3] ath10k: Fix shared WEP

2014-11-23 Thread Sujith Manoharan
From: Sujith Manoharan When static keys are used in shared WEP, when a station is associated, message 3 is sent with an encrypted payload. But, for subsequent authentications that are triggered without a deauth, the auth frame is decrypted by the HW. To handle this, check if the WEP keys have al

RE: wireless-regdb: Update regulatory rules for New Zealand (NZ) on 5GHz and 60 GHz [UNCLASSIFIED]

2014-11-23 Thread Peter Gent
Hi, John - thank you for the suggested patch. We have a couple of queries and comments on what is proposed so far for the list. 1) Our top 2 GHz in the 60 GHz band "64000 - 66000 MHz" is indoor only and comments are edited as such 2) Is it possible to define an indoor / outdoor limit inside t

pull request: firmware updates for Intel Wireless devices 3160/7260/7265

2014-11-23 Thread Emmanuel Grumbach
Hello, Intel officially released a new spin of the -9 version of the firmware for devices 3160, 7260 and 7265. This release had been announced a while ago, but the linux-firmware.git's maintainers didn't pick it up. This is a new pull request with almost the exact same -9 version - it has one m

[PATCH] iwlwifi: mvm: check TLV flag before trying to use hotspot firmware commands

2014-11-23 Thread Emmanuel Grumbach
From: Luciano Coelho Older firmwares do not provide support for the HOT_SPOT_CMD command. Check for the appropriate TLV flag that declares hotspot support in the firmware to prevent a firmware assertion failure that can be triggered from the userspace, Cc: sta...@vger.kernel.org [3.17+] Signed-o

pull request: iwlwifi 2014-11-23

2014-11-23 Thread Emmanuel Grumbach
Hi John, I have a trivial patch for 3.18. details below. Thanks! The following changes since commit 87dd634ae72bb8f6d0dd12f1cbbc67c7da6dba3b: iwlwifi: pcie: fix prph dump length (2014-11-11 07:24:57 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/gi

[PATCH v3 1/3] cfg80211: leave invalid channels on regdomain change

2014-11-23 Thread Arik Nemtsov
When the regulatory settings change, some channels might become invalid. Disconnect interfaces acting on these channels, after giving userspace code a grace period to leave them. This mode is currently opt-in, and not all interface operating modes are supported for regulatory-enforcement checks. A

[PATCH v3 2/3] cfg80211: allow wiphy specific regdomain management

2014-11-23 Thread Arik Nemtsov
From: Jonathan Doron Add a new regulatory flag that allows a driver to manage regdomain changes/updates for its own wiphy. A self-managed wiphys only employs regulatory information obtained from the FW and driver and does not use other cfg80211 sources like beacon-hints, country-code IEs and hint

[PATCH v3 3/3] cfg80211: Allow usermode to query wiphy specific regd info

2014-11-23 Thread Arik Nemtsov
From: Jonathan Doron Allow usermode to query wiphy-specific regd info, for drivers that use wiphy-specific regulatory management. Use the existing API for sending regdomain info to usermode, but return the wiphy-specific regd in case wiphy index is provided and the driver employs wiphy-specific

Re: [PATCH v3] ath3k: Add support of MCI 13d3:3408 bt device

2014-11-23 Thread Dmitry Tunin
After some testing on a few laptops it looks like the firmware loads always correctly only using AR3012 variant. So the correct patch follows --- diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c index d85ced2..086240c 100644 --- a/drivers/bluetooth/ath3k.c +++ b/drivers/blueto

Re: BCM4313 & brcmsmac & 3.12: only semi-working?

2014-11-23 Thread Arend van Spriel
On 19-11-14 22:00, Michael Tokarev wrote: > 19.11.2014 22:58, Michael Tokarev wrote: >> 19.11.2014 20:54, Arend van Spriel wrote: > [] >>> I submitted two patches upstream and additionally I have attached two other >>> that are still under review. Could you try these patches and sent me the >>> c