linux-stable.git/net/wireless/mesh.c, branch linux-3.8.y

cfg80211: fix channel error on mesh join

2012-12-03T10:24:49+00:00

Fix an error on mesh join when no channel has been
explicitly set beforehand.

Also remove a double semicolon.

Signed-off-by: Marco Porsch 
Signed-off-by: Johannes Berg

nl80211/cfg80211: support VHT channel configuration

2012-11-26T11:42:59+00:00

Change nl80211 to support specifying a VHT (or HT)
using the control channel frequency (as before) and
new attributes for the channel width and first and
second center frequency. The old channel type is of
course still supported for HT.

Also change the cfg80211 channel definition struct
to support these by adding the relevant fields to
it (and removing the _type field.)

This also adds new helper functions:
 - cfg80211_chandef_create to create a channel def
   struct given the control channel and channel type,
 - cfg80211_chandef_identical to check if two channel
   definitions are identical
 - cfg80211_chandef_compatible to check if the given
   channel definitions are compatible, and return the
   wider of the two

This isn't entirely complete, but that doesn't matter
until we have a driver using it. In particular, it's
missing
 - regulatory checks on the usable bandwidth (if that
   even makes sense)
 - regulatory TX power (database can't deal with it)
 - a proper channel compatibility calculation for the
   new channel types

Signed-off-by: Johannes Berg

cfg80211: pass a channel definition struct

2012-11-26T11:42:58+00:00

Instead of passing a channel pointer and channel type
to all functions and driver methods, pass a new channel
definition struct. Right now, this struct contains just
the control channel and channel type, but for VHT this
will change.

Also, add a small inline cfg80211_get_chandef_type() so
that drivers don't need to use the _type field of the
new structure all the time, which will change.

Signed-off-by: Johannes Berg

cfg80211: add cfg80211 exported function tracing

2012-10-18T08:53:38+00:00

Also add tracing to the API functions that drivers
(and mac80211) can call in cfg80211.

Signed-off-by: Beni Lev 
Reviewed-by: Emmanuel Grumbach 
Reviewed-by: Johannes Berg 
Signed-off-by: Johannes Berg

cfg80211: add wrappers for registered_device_ops

2012-10-18T08:53:37+00:00

This will allow adding central tracing like in mac80211.

Signed-off-by: Hila Gonen 
Reviewed-by: Emmanuel Grumbach 
Reviewed-by: Johannes Berg 
Signed-off-by: Johannes Berg

cfg80211: respect iface combinations when starting operation

2012-06-29T11:39:19+00:00

devlist_mtx locking is changed to accomodate changes.

Signed-off-by: Michal Kazior 
Signed-off-by: Johannes Berg

cfg80211: add channel tracking for AP and mesh

2012-06-29T11:39:15+00:00

We need to know which channel is used by a running
AP and mesh for channel context accounting and
finding matching/active interface combination.

STA/IBSS have current_bss already which allows us
to check which channel a vif is tuned to.
Non-fixed channel IBSS can be handled with
additional changes.

Monitor mode is going to be handled differently.

Signed-off-by: Michal Kazior 
Signed-off-by: Johannes Berg

{nl,cfg,mac}80211: implement dot11MeshHWMPconfirmationInterval

2012-06-18T11:55:15+00:00

As defined in section 13.10.9.3 Case D (802.11-2012), this
control variable is used to limit the mesh STA to send only
one PREQ to a root mesh STA within this interval of time
(in TUs). The default value for this variable is set to
2000 TUs. However, for current implementation, the maximum
configurable of dot11MeshHWMPconfirmationInterval is
restricted by dot11MeshHWMPactivePathTimeout.

Signed-off-by: Chun-Yeow Yeoh 
[line-break commit log]
Signed-off-by: Johannes Berg

{nl,cfg,mac}80211: implement dot11MeshHWMProotInterval and dot11MeshHWMPactivePathToRootTimeout

2012-06-14T07:08:22+00:00

Add the mesh configuration parameters dot11MeshHWMProotInterval
and dot11MeshHWMPactivePathToRootTimeout to be used by
proactive PREQ mechanism.

Signed-off-by: Chun-Yeow Yeoh 
[line-break commit log]
Signed-off-by: Johannes Berg

cfg80211: clarify set_channel APIs

2012-06-06T19:18:17+00:00

Now that we've removed all uses of the set_channel
API except for the monitor channel and in libertas,
clarify this. Split the libertas mesh use into a
new libertas_set_mesh_channel() operation, just to
keep backward compatibility, and rename the normal
set_channel() to set_monitor_channel().

Also describe the desired set_monitor_channel()
semantics more clearly.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville