diff options
author | Johannes Berg <johannes.berg@intel.com> | 2012-05-16 17:50:20 -0400 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2012-06-05 15:32:18 -0400 |
commit | cc1d2806bf06ab92268343d26eb3d8d8f00f8bc9 (patch) | |
tree | b14ffa920d616470715e715df49f990bfdcf12ae /include | |
parent | 685d12a1929f274bd91497e33b4255fe164ac8ec (diff) |
cfg80211: provide channel to join_mesh function
Just like the AP mode patch, instead of setting
the channel and then joining the mesh network,
provide the channel to join the network on to
the join_mesh() function.
Like in AP mode, you can also give the channel
to the join-mesh nl80211 command now.
Unlike AP mode, it picks a default channel if
none was given.
As libertas uses mesh mode interfaces but has
no join_mesh callback and we can't simply break
it, keep some compatibility code for that case
and configure the channel directly for it.
In the non-libertas case, where we store the
channel until join, allow setting it while the
interface is down.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'include')
-rw-r--r-- | include/net/cfg80211.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h index a54fb895f613..4c90c44b8b75 100644 --- a/include/net/cfg80211.h +++ b/include/net/cfg80211.h | |||
@@ -831,6 +831,8 @@ struct mesh_config { | |||
831 | 831 | ||
832 | /** | 832 | /** |
833 | * struct mesh_setup - 802.11s mesh setup configuration | 833 | * struct mesh_setup - 802.11s mesh setup configuration |
834 | * @channel: the channel to start the mesh network on | ||
835 | * @channel_type: the channel type to use | ||
834 | * @mesh_id: the mesh ID | 836 | * @mesh_id: the mesh ID |
835 | * @mesh_id_len: length of the mesh ID, at least 1 and at most 32 bytes | 837 | * @mesh_id_len: length of the mesh ID, at least 1 and at most 32 bytes |
836 | * @sync_method: which synchronization method to use | 838 | * @sync_method: which synchronization method to use |
@@ -845,6 +847,8 @@ struct mesh_config { | |||
845 | * These parameters are fixed when the mesh is created. | 847 | * These parameters are fixed when the mesh is created. |
846 | */ | 848 | */ |
847 | struct mesh_setup { | 849 | struct mesh_setup { |
850 | struct ieee80211_channel *channel; | ||
851 | enum nl80211_channel_type channel_type; | ||
848 | const u8 *mesh_id; | 852 | const u8 *mesh_id; |
849 | u8 mesh_id_len; | 853 | u8 mesh_id_len; |
850 | u8 sync_method; | 854 | u8 sync_method; |