linux-toradex.git/net/wireless/wext-compat.c, branch v3.9-rc2

wext: explicitly cast -110 to u8

2012-12-07T10:58:26+00:00

This doesn't generate any different code, but will
suppress a spurious smatch warning.

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: allow per interface TX power setting

2012-10-30T08:11:34+00:00

The TX power setting is currently per wiphy (hardware
device) but with multi-channel capabilities that doesn't
make much sense any more.

Allow drivers (and mac80211) to advertise support for
per-interface TX power configuration. When the TX power
is configured for the wiphy, the wdev will be NULL and
the driver can still handle that, but when a wdev is
given the TX power can be set only for that wdev now.

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/mac80211: re-add get_channel operation

2012-07-13T14:16:11+00:00

This essentially reverts commit 2e165b818456 but
introduces the get_channel operation with a new
wireless_dev argument so that you can retrieve
the channel per interface. This is necessary as
even though we can track all interface channels
(except monitor) we can't track the channel type
used.

Signed-off-by: Johannes Berg

cfg80211/mac80211: remove .get_channel

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

We do not need it anymore since cfg80211 tracks
monitor channel and monitor channel type.

Signed-off-by: Michal Kazior 
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

cfg80211: provide channel to join_mesh function

2012-06-05T19:32:18+00:00

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 
Signed-off-by: John W. Linville

cfg80211: disallow setting channel on WDS interfaces

2012-06-05T19:32:17+00:00

If it worked (Felix says it doesn't right now), the
typical use-case for WDS interfaces would be to be
slaved to AP mode interfaces. Therefore, it isn't
necessary to set the channel on WDS interfaces. As
they don't support powersave or anything like that,
they also couldn't use a different channel anyway.

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