devices to manage
regdomain changes exclusively for their own wiphy. These devices do not update
the cfg80211 regdomain and are unaffected by hints external to the device/FW.
Introduce a new API to allow these devices to set their own regdomain.
Arik Nemtsov (2):
cfg80211: introduce regulatory flags
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
---
include/net/regulatory.h | 6 +++
net/wireless/reg.c
From: Jonathan Doron j...@wizery.com
Some channels fields were not being updated in the custom regulatory
path. Update them according to the code in handle_channel().
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/wireless
regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/net/cfg80211.h | 14
include/net/regulatory.h | 9 +
include/uapi/linux/nl80211.h
wiphy-specific management. This implies user and kernel-mode
support for the feature and is backward compatible.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 6 +
net/wireless/nl80211.c
On Wed, Nov 5, 2014 at 5:23 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com wrote:
+ * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
+ * regulatory information came from the driver and not from
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/linux/ieee80211.h | 25
net/mac80211/ieee80211_i.h | 4
net/mac80211/mlme.c| 12 ++
net/mac80211/status.c | 55
-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
net/mac80211/cfg.c | 3 ++-
net/mac80211/ieee80211_i.h | 3 +--
net/mac80211/sta_info.c| 3 ++-
net/mac80211/tx.c | 23 +++
4 files changed, 16 insertions(+), 16
From: Liad Kaufman liad.kauf...@intel.com
Allows setting of an skb's flags - if needed - when calling
ieee80211_subif_start_xmit().
Signed-off-by: Liad Kaufman liad.kauf...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
net/mac80211
-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/linux/ieee80211.h| 6 ++
include/uapi/linux/nl80211.h | 3 +++
net/mac80211/tdls.c | 9 ++---
3 files changed, 15 insertions(+), 3
of the channel-switch all communication between the
relevant TDLS peers will continue on the base channel.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/net/cfg80211.h | 8
Add the BSS coex IE in case we support HT40 channels, as mandated by
section 8.5.13 in IEEE802.11 2012.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/linux/ieee80211.h | 3 +++
net
Split the data-generating from the Tx-sending functionality, as we do
not want to send templates to the lower driver. Also add an optional
chandef argument to the data-generating portion. It will be used for
channel-switch templates.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed
From: Liad Kaufman liad.kauf...@intel.com
If the HW supports IEEE80211_HW_QUEUE_CONTROL, allow
flushing only specific queues rather than all of them.
Signed-off-by: Liad Kaufman liad.kauf...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
net/mac80211/cfg.c | 7 +++
net/mac80211/debugfs_sta.c | 5 +++--
net/mac80211/ieee80211_i.h | 3 +++
net/mac80211/mlme.c| 3 +++
net/mac80211
When receiving a TDLS channel switch request or response, parse the frame
and call a new tdls_recv_channel_switch op in the low level driver with
the parsed data.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov
that the allocated TID is indeed unused, this patch
introduces an API for blocking the driver from TXing on that
TID.
Signed-off-by: Liad Kaufman liad.kauf...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/net/mac80211.h | 37
-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
net/mac80211/ieee80211_i.h | 3 +++
net/mac80211/tx.c | 31 +++
2 files changed, 34 insertions(+)
diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
These are used in TDLS channel switching code.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov a...@wizery.com
---
include/linux/ieee80211.h | 15 +++
net/mac80211/ieee80211_i.h | 2 ++
net/mac80211
From: Johannes Berg johannes.b...@intel.com
Factor out the 802.11 header building code from the xmit function
to be able to use it separately in a later commit.
While at it, fix up some documentation.
Signed-off-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Arik Nemtsov
On Sun, Nov 9, 2014 at 9:50 PM, Arend van Spriel ar...@broadcom.com wrote:
On 11/09/14 17:50, Arik Nemtsov wrote:
Introduce commands to initiate and cancel TDLS channel-switching. Once
TDLS channel-switching is started, the lower level driver is responsible
for continually initiating channel
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
---
include
wiphy-specific management. This implies user and kernel-mode
support for the feature and is backward compatible.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 6 +
net/wireless/nl80211.c
regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/net/cfg80211.h | 14
include/net/regulatory.h | 9 +
include/uapi/linux/nl80211.h
On Fri, Nov 14, 2014 at 12:45 AM, Luis R. Rodriguez mcg...@suse.com wrote:
+ * @REGULATORY_ENFORCE_CHANNELS: the regulatory core will make sure all
+ * interfaces on this wiphy reside on allowed channels. Upon a regdomain
+ * change, the interfaces are given a grace period to disconnect or
On Fri, Nov 14, 2014 at 12:55 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Thu, Nov 13, 2014 at 06:13:37PM +0200, Arik Nemtsov wrote:
From: Jonathan Doron j...@wizery.com
Some channels fields were not being updated in the custom regulatory
path. Update them according to the code
On Fri, Nov 14, 2014 at 1:13 AM, Luis R. Rodriguez mcg...@suse.com wrote:
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
Explicitly initialize the DFS state and beacon found state when handling
channels in the custom regulatory path.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Acked-by: Luis R. Rodriguez mcg...@suse.com
---
net/wireless/reg.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net
of the channel-switch all communication between the
relevant TDLS peers will continue on the base channel.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Johannes Berg johannes.b...@intel.com
---
v2: document the operating class attribute
include/net/cfg80211.h | 14
On Wed, Nov 19, 2014 at 1:22 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sun, 2014-11-09 at 18:50 +0200, Arik Nemtsov wrote:
+ if (WARN_ON(tid = IEEE80211_NUM_TIDS))
+ return -EINVAL;
That validates 16
+ queues = BIT(sdata-vif.hw_queue[ieee802_1d_to_ac[tid
On Wed, Nov 19, 2014 at 1:41 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2014-11-19 at 13:40 +0200, Arik Nemtsov wrote:
On Wed, Nov 19, 2014 at 1:22 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sun, 2014-11-09 at 18:50 +0200, Arik Nemtsov wrote:
+ if (WARN_ON
From: Liad Kaufman liad.kauf...@intel.com
In TDLS (e.g., TDLS off-channel) there is a requirement for
some drivers to supply an unused TID between the AP and the
device to the FW, to allow sending PTI requests and to allow
the FW to aggregate on a specific TID for better throughput.
To ensure
On Thu, Nov 20, 2014 at 10:27 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 16, 2014 at 01:06:00PM +0200, Arik Nemtsov wrote:
On Fri, Nov 14, 2014 at 1:11 AM, Luis R. Rodriguez mcg...@suse.com wrote:
index a4d2792..656a1b1 100644
--- a/net/wireless/core.c
+++ b/net/wireless
On Thu, Nov 20, 2014 at 10:54 PM, Luis R. Rodriguez mcg...@suse.com wrote:
Then it gets the global one, and it knows it via a wiphy attribute:
(wiphy-regulatory_flags REGULATORY_WIPHY_SELF_MANAGED)
+ (nla_put_flag(msg, NL80211_ATTR_WIPHY_SELF_MANAGED_REG)))
+
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/net/cfg80211.h | 16 +
include
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
Please rename to REGULATORY_IGNORE_STALE_KICKOFF, also please add
some information about the amount current of grace period used,
and types of interfaces supported. Since this is a regulatory flag
this information will
On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:21PM +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
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:19PM +0200, Arik Nemtsov wrote:
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code a grace
. A wiphy that wishes to use
the new enforcement code must specify an appropriate regulatory flag,
and all its supported interface modes must be supported by the chekcing
code.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/net/regulatory.h | 12 ++
net/wireless/core.c
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can distinguish
them as such.
Signed-off-by: Arik Nemtsov
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/net/cfg80211.h | 20
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
Rest assured, I have an iw version that prints all the regdomains. I just
need a bit of time to clean it up.
include/uapi/linux/nl80211.h | 16
On Wed, Nov 26, 2014 at 11:43 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 4:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
We're not checking here if this was a managed wiphy or not, we
want userspace to be able to tell if a wiphy was managed or not.
Ah I see what
. A wiphy that wishes to use
the new enforcement code must specify an appropriate regulatory flag,
and all its supported interface modes must be supported by the chekcing
code.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
---
include/net
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can distinguish
them as such.
Signed-off-by: Arik Nemtsov
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
v5: don't return all regdomains if a specific wiphy is requested
include/uapi/linux/nl80211.h | 16 +-
net/wireless/nl80211.c | 127
On Thu, Nov 27, 2014 at 5:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Thu, Nov 27, 2014 at 09:12:11AM +0200, Arik Nemtsov wrote:
On Wed, Nov 26, 2014 at 11:43 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 4:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
We're
On Sat, Nov 29, 2014 at 12:00 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Fri, Nov 28, 2014 at 02:46:27PM +0100, Johannes Berg wrote:
On Thu, 2014-11-27 at 09:44 +0200, Arik Nemtsov wrote:
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists
On Sun, Nov 30, 2014 at 2:32 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sun, 2014-11-30 at 14:26 +0200, Arik Nemtsov wrote:
I think Johannes' point was that it's easy to overrun the message size
if there are a lot of wiphys.
Yes.
So I'll simply add an iterator over all wiphys
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
Ilan Peer mentioned this bug privately, so I thought I'd roll it up into
this patch-set
net/wireless/reg.c | 8
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
Signed-off-by: Arik Nemtsov a...@wizery.com
---
nl80211.h | 143 ++
1 file changed, 135 insertions(+), 8 deletions(-)
diff --git a/nl80211.h b/nl80211.h
index f7daae5..9884464 100644
--- a/nl80211.h
+++ b/nl80211.h
@@ -252,7 +252,9
When a phy is given, print only its regdomain. Otherwise, use the newly
implement dump functionality to print all regdomains in the system.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
index 9af8e7e..a02c982 100644
--- a/reg.c
+++ b/reg.c
@@ -127,7 +127,7 @@ static int print_reg_handler(struct nl_msg *msg, void *arg)
struct nlattr
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
index 9af8e7e..a02c982 100644
--- a/reg.c
+++ b/reg.c
@@ -127,7 +127,7 @@ static int print_reg_handler(struct nl_msg *msg, void *arg)
struct nlattr
Signed-off-by: Arik Nemtsov a...@wizery.com
---
nl80211.h | 143 ++
1 file changed, 135 insertions(+), 8 deletions(-)
diff --git a/nl80211.h b/nl80211.h
index f7daae5..9884464 100644
--- a/nl80211.h
+++ b/nl80211.h
@@ -252,7 +252,9
These were added to cfg80211 recently
Signed-off-by: Arik Nemtsov a...@wizery.com
---
v2: remove XXX from title, apparently the ML doesn't like them :)
reg.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/reg.c b/reg.c
index e1bb0d2..9af8e7e 100644
--- a/reg.c
+++ b/reg.c
@@ -199,6
When a phy is given, print only its regdomain. Otherwise, use the newly
implement dump functionality to print all regdomains in the system.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
reg.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/reg.c b/reg.c
Signed-off-by: Arik Nemtsov a...@wizery.com
---
info.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/info.c b/info.c
index 7499290..7f8c832 100644
--- a/info.c
+++ b/info.c
@@ -587,6 +587,8 @@ broken_combination:
printf(\tDevice supports WMM-AC admission (TSPECs)\n
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 8 +-
net/wireless/nl80211.c | 178 +++
net/wireless/reg.c
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
---
net/wireless/reg.c | 8 +++-
1 file changed, 7 insertions(+), 1
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
v8: remove bogus documentation from cfg80211.h
include/uapi/linux/nl80211.h | 8 +-
net/wireless/nl80211.c | 178
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
---
net/wireless/reg.c | 8 +++-
1 file changed, 7 insertions(+), 1
In the already-set and intersect case of a driver-hint, the previous
wiphy regdomain was not freed before being reset with a copy of the
cfg80211 regdomain.
Cc: sta...@vger.kernel.org
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/wireless/reg.c | 5 -
1 file changed, 4
registration, so this didn't matter. The previous approach doesn't scale
well to self-managed regulatory devices, particularly when a more
permissive regdom is applied after a restrictive one.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/wireless/reg.c | 5 ++---
1 file changed, 2
On Fri, Dec 12, 2014 at 2:41 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sun, 2014-12-07 at 18:03 +0200, Arik Nemtsov wrote:
The custom-reg handling function can currently only add flags to a given
channel. This results in stale flags being left applied. In some cases
a channel
When a phy is given, print only its regdomain. Otherwise, use the newly
implement dump functionality to print all regdomains in the system.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
v2: fix reg get for older kernels
reg.c | 40
1 file changed, 36
On Fri, Dec 12, 2014 at 2:37 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2014-12-03 at 18:08 +0200, Arik Nemtsov wrote:
* @NL80211_CMD_GET_REG: ask the wireless core to send us its currently set
- * regulatory domain.
+ * regulatory domain. If %NL80211_ATTR_WIPHY
On Fri, Dec 12, 2014 at 2:39 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2014-12-03 at 18:08 +0200, Arik Nemtsov wrote:
+void nl80211_send_reg_change_event(struct regulatory_request *request)
+{
+ nl80211_common_reg_change_event(NL80211_CMD_REG_CHANGE, request
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 10 ++-
net/wireless/nl80211.c | 173 ++-
net/wireless/reg.c
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
registration, so this didn't matter. The previous approach doesn't scale
well to self-managed regulatory devices, particularly when a more
permissive regdom is applied after a restrictive one.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/wireless/reg.c | 16 +---
1 file changed
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
.
Add a new attribute for each wiphy-specific regdomain, for usermode to
identify it as such.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 10 ++-
net/wireless/nl80211.c | 173 ++-
net/wireless/reg.c
registration, so this didn't matter. The previous approach doesn't scale
well to self-managed regulatory devices, particularly when a more
permissive regdom is applied after a restrictive one.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/wireless/reg.c | 16 +---
1 file changed
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
notification. The regulatory core also takes care
enforce regulatory restrictions, in case some interfaces are on
forbidden channels.
Signed-off-by: Jonathan Doron jonathanx.do...@intel.com
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Luis R. Rodriguez mcg...@suse.com
---
v10
Some network cards (Intel) produce per-channel regdomains and rely on
cfg80211 to merge rules as needed. This hits the max rules limit and
fails.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
include/uapi/linux/nl80211.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Dec 18, 2014 at 3:56 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2014-12-17 at 18:00 +0200, Arik Nemtsov wrote:
Some network cards (Intel) produce per-channel regdomains and rely on
cfg80211 to merge rules as needed. This hits the max rules limit and
fails.
Maybe we
On Mon, Dec 22, 2014 at 3:26 PM, Arend van Spriel ar...@broadcom.com wrote:
On 12/22/14 14:14, Johannes Berg wrote:
On Mon, 2014-12-22 at 14:13 +0100, Arend van Spriel wrote:
On 12/22/14 13:58, Johannes Berg wrote:
By the way - I know now that the proprietary Broadcom driver has the
same
. HT20 was explicitly required in the chandef, while not a requirement
for TDLS off-channel.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
net/mac80211/tdls.c | 17 -
1 file changed, 12 insertions(+), 5 deletions
if the
wdev is active and saves the channel under the wdev lock. The second part
will check actual channel validity according to type.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
Reviewed-by: Ilan Peer ilan.p...@intel.com
Reviewed-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
Requires
The patch 40a11ca mac80211: check if channels allow 80 MHz for VHT
probe requests considered disabled channels as VHT enabled, and
mistakenly sent out probe-requests with the VHT IE.
Signed-off-by: Arik Nemtsov arikx.nemt...@intel.com
---
net/mac80211/util.c | 10 ++
1 file changed, 6
(since the !sta goes away)
Signed-off-by: Johannes Berg johannes.b...@intel.com
Reviewed-by: Arik Nemtsov a...@wizery.com
Arik
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Tue, Jan 20, 2015 at 2:35 PM, Janusz Dziedzic
janusz.dzied...@tieto.com wrote:
Add VHT80/VHT160 support for IBSS.
Drivers could activate this feature by
setting NL80211_FEATURE_VHT_IBSS flag.
Signed-off-by: Janusz Dziedzic janusz.dzied...@tieto.com
[...]
+u8
On Fri, Jan 23, 2015 at 12:04 PM, Johannes Berg
johan...@sipsolutions.net wrote:
+++ b/net/mac80211/util.c
@@ -2317,6 +2317,41 @@ u8 *ieee80211_ie_build_ht_oper(u8 *pos, struct
ieee80211_sta_ht_cap *ht_cap,
return pos + sizeof(struct ieee80211_ht_operation);
}
+u8
On Mon, Jan 26, 2015 at 10:26 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sun, 2015-01-25 at 12:30 +0200, Arik Nemtsov wrote:
+ switch (chandef-width) {
+ case NL80211_CHAN_WIDTH_80:
+ vht_oper-chan_width = IEEE80211_VHT_CHANWIDTH_80MHZ
Don't define iw build target in the regular Makefile which gets
included. This confuses the Android build system (coincides with module
name).
Also correct libnl_2 to a be static library, as compiled on Android.
Signed-off-by: Arik Nemtsov a...@wizery.com
---
Android.mk | 3 ++-
Makefile | 2
Otherwise Android gets confused and tries to build the Makefile target
Signed-off-by: Arik Nemtsov a...@wizery.com
---
Android.mk | 1 +
Makefile | 2 ++
2 files changed, 3 insertions(+)
diff --git a/Android.mk b/Android.mk
index 8afda1d..00c8c49 100644
--- a/Android.mk
+++ b/Android.mk
On Tue, Jan 6, 2015 at 3:59 PM, Johannes Berg johan...@sipsolutions.net wrote:
On Tue, 2015-01-06 at 11:56 +0100, Johannes Berg wrote:
On Thu, 2015-01-01 at 13:42 +0200, Arik Nemtsov wrote:
When a system contains only self-managed regulatory devices all hints
from the regulatory core
On Tue, Jan 13, 2015 at 12:30 PM, Julian Calaby julian.cal...@gmail.com wrote:
Hi Arik,
On Tue, Jan 13, 2015 at 9:11 PM, Arik Nemtsov a...@wizery.com wrote:
On Tue, Jan 13, 2015 at 6:26 AM, Julian Calaby julian.cal...@gmail.com
wrote:
Hi Arik,
On Thu, Jan 8, 2015 at 1:47 AM, Arik Nemtsov
1 - 100 of 133 matches
Mail list logo
