This makes it easier to write (semi-)automated synchronization and
validation scripts against external databases. I'd assume this order was
already supposed to be used, but couple of the countries have been
placed in incorrect locations in the file over the years.
Signed-off-by: Jouni Malinen
On 12-11-14 16:23, Felipe Contreras wrote:
On Wed, Nov 12, 2014 at 4:40 AM, Arend van Spriel ar...@broadcom.com wrote:
On 11-11-14 23:32, Felipe Contreras wrote:
On Sun, Nov 9, 2014 at 4:46 AM, Arend van Spriel ar...@broadcom.com wrote:
Could you share the nvram obtained from EFI? Also please
This patch adds WMM support for TDLS link. Patch
add WMM info IE for TDLS setup request/response frames
while WMM parameter for TDLS confirm frame.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/tdls.c | 55
RX packet descriptor structure has recently changed in FW.
This patch updates rxpd accordingly.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/fw.h | 1 +
1 file changed, 1 insertion(+)
diff --git
When Teardown event from FW is indicated to userspace, userspace
would trigger tdls_oper handler to disable TDLS link.
We need not do this explicitly here.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/sta_event.c | 3
This patch adds auto TDLS support to mwifiex.
Auto TDLS functionality works as follows:
1. Whenever userspace application has triggered TDLS connection with
any peer, driver would store this peer mac address details in its database.
2. After this driver whenever driver receives packet on direct
This patch adds support for parsing TDLS discovery
frames. After parsing, we update peer RSSI information.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/util.c | 38 +
1 file changed,
Auto TDLS support is enabled per device. As of now add this
feature only for SD8887.
Signed-off-by: Avinash Patil pat...@marvell.com
Signed-off-by: Cathy Luo c...@marvell.com
---
drivers/net/wireless/mwifiex/init.c | 1 -
drivers/net/wireless/mwifiex/sdio.c | 2 ++
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages to check if there are wireless devices in the system.
Hence my question, can we
On Thu, 2014-11-13 at 13:33 +0100, Stanislaw Gruszka wrote:
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages to check if there
With the alias cfg80211 module is loaded on systems without the wireless
hardware when user-space use nl80211 to discover if there are wireless
devices, what is considered as resources wastage. On systems with
wireless hardware cfg80211 module will be loaded anyway.
Cc: Marcel Holtmann
Hi Johannes,
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages to check if there are wireless devices in the system.
Hence
Hi
On Thu, Nov 13, 2014 at 10:36:17PM +0900, Marcel Holtmann wrote:
With the alias cfg80211 module is loaded on systems without the wireless
hardware when user-space use nl80211 to discover if there are wireless
devices, what is considered as resources wastage. On systems with
wireless
Hi Stanislaw,
With the alias cfg80211 module is loaded on systems without the wireless
hardware when user-space use nl80211 to discover if there are wireless
devices, what is considered as resources wastage. On systems with
wireless hardware cfg80211 module will be loaded anyway.
Cc:
Replace NL80211_ATTR_IFACE_SOCKET_OWNER attribute with more generic
NL80211_ATTR_SOCKET_OWNER that can be used with other commands
that interface creation.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/uapi/linux/nl80211.h | 7 ---
net/wireless/nl80211.c | 4
An attribute NL80211_ATTR_SOCKET_OWNER can be set by the scan initiator.
If present, the attribute will cause the scan to be stopped if the client
dies.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/net/cfg80211.h | 2 ++
include/uapi/linux/nl80211.h | 3 +++
Hi,
v4:
- rtnl locking issues fixed in patch 2
v3:
- backward compatibility define tweaked in patch 1
- added missing signed-off-by:
v2:
- split the patch
- In patch 1, use a generic NL80211_ATTR_SOCKET_OWNER attribute and
convert the old code that uses NL80211_ATTR_IFACE_SOCKET_OWNER to
On Thu, 2014-11-13 at 15:49 +0200, Jukka Rissanen wrote:
An attribute NL80211_ATTR_SOCKET_OWNER can be set by the scan initiator.
If present, the attribute will cause the scan to be stopped if the client
dies.
+ if (rtnl_trylock()) {
+ __cfg80211_stop_sched_scan(rdev, false);
Hi,
v5:
- discarded the locking changes in v4
- instead of trying to schedule sched_scan_stop worker from
struct cfg80211_sched_scan_request, move the worker to wiphy
as that makes it easier to manage the sched_scan_stop worker.
There are also one scheduled scan / wiphy so it is also
Replace NL80211_ATTR_IFACE_SOCKET_OWNER attribute with more generic
NL80211_ATTR_SOCKET_OWNER that can be used with other commands
that interface creation.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/uapi/linux/nl80211.h | 7 ---
net/wireless/nl80211.c | 4
An attribute NL80211_ATTR_SOCKET_OWNER can be set by the scan initiator.
If present, the attribute will cause the scan to be stopped if the client
dies.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/net/cfg80211.h | 1 +
include/uapi/linux/nl80211.h | 3 +++
On Thu, Nov 13, 2014 at 12:53 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Nov 5, 2014 at 1:18 AM, Arik Nemtsov a...@wizery.com wrote:
On Wed, Nov 5, 2014 at 5:16 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com
2. And then if userspace sends a wiphy idx to the NL80211_CMD_GET_REG,
we'll return wiphy-regd for that case as well?
That's right, for now we'd be able to send the regd when either
NL80211_ATTR_WIPHY_SELF_MANAGED_REG is set or when
NL80211_ATTR_WIPHY_SELF_MANAGED_REG is not set but
On Thu, Nov 13, 2014 at 1:07 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Nov 5, 2014 at 12:41 AM, Arik Nemtsov a...@wizery.com wrote:
On Wed, Nov 5, 2014 at 5:21 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com
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.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
---
From: Jonathan Doron j...@wizery.com
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
From: Jonathan Doron j...@wizery.com
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
In this case the regdomain is local to the driver, and it does not use
the shared cfg80211 regdomain. It also implies that the driver does not
wish to get
IRQs are suppressed if ah == NULL and ATH_OP_INVALID being set in
common-op_flags. Close a short time window between those two.
Signed-off-by: Felix Fietkau n...@openwrt.org
---
drivers/net/wireless/ath/ath9k/init.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Instead of killing interrupts during reset when the first one happens,
kill them before issuing the reset.
This fixes an easy to reproduce crash with multiple cards sharing the
same IRQ.
Cc: sta...@vger.kernel.org
Signed-off-by: Felix Fietkau n...@openwrt.org
---
Closes another small IRQ handler race
Signed-off-by: Felix Fietkau n...@openwrt.org
---
drivers/net/wireless/ath/ath9k/main.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/main.c
index
Hi,
This is a question not about the wireless properties of the Atheros
AR93xx, but about the PCIe bus reset behavior. We have a user reporting
errors with a TP-LINK TL-WDN4800 and I've acquired the same card and
have been able to reproduce the error on two systems. The problem is
that if we
Johannes, Jouni, please review the comment about WLAN_REASON_DEAUTH_LEAVING
below.
On Thu, Nov 13, 2014 at 06:13:36PM +0200, Arik Nemtsov wrote:
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code
On Thu, Nov 13, 2014 at 06:13:39PM +0200, Arik Nemtsov wrote:
From: Jonathan Doron j...@wizery.com
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
On Thu, Sep 11, 2014 at 1:43 PM, Kalle Valo kv...@qca.qualcomm.com wrote:
Kalle Valo kv...@qca.qualcomm.com writes:
latest version of my testmode patches. Getting closer, more or less cosmetic
changes this time :)
While looking through this patchset (sorry it took two months), I have
to
On Thu, 2014-11-13 at 22:41 +0900, Marcel Holtmann wrote:
Hi Johannes,
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages
On Thu, 2014-11-13 at 22:48 +0900, Marcel Holtmann wrote:
Hi Stanislaw,
With the alias cfg80211 module is loaded on systems without the wireless
hardware when user-space use nl80211 to discover if there are wireless
devices, what is considered as resources wastage. On systems with
Secured mesh encrypts the unicast mgmt frame using the same
key that used for encrypting the unicast data frame. The patch
ath9k_htc_firmware: fix the offset of CCMP header for mesh
data frame applied to open-ath9k-htc-firmware allows the
ath9k_htc to be loaded without nohwcrypt=1. Unfortunately,
Use the inline function instead of directly indexing the array.
This allows some architectures with hardware instructions for bit
reversals to eliminate the array.
Signed-off-by: Joe Perches j...@perches.com
Signed-off-by: Yalin Wang yalin.w...@sonymobile.com
---
From: Joe Perches [mailto:j...@perches.com]
Sent: Friday, November 14, 2014 1:33 PM
To: Wang, Yalin
Cc: 'chunk...@googlemail.com'; 'linvi...@tuxdriver.com'; 'linux-
wirel...@vger.kernel.org'; 'net...@vger.kernel.org'; 'linux-
ker...@vger.kernel.org'
Subject: Re: [PATCH] carl9170: Convert
Hi Luca,
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages to check if there are wireless devices in the system.
Hence my
Hi Dan,
I've updated wireless code on RHEL and get complain that now
cfg80211 and rfkill modules are loaded on machines that do not have
wireless hardware. Modules are auto-loaded because NetworkManager send
nl80211 messages to check if there are wireless devices in the system.
Hence my
41 matches
Mail list logo
