1. 01 12月, 2012 21 次提交
  2. 27 11月, 2012 6 次提交
  3. 26 11月, 2012 13 次提交
    • J
      cfg80211: fix some tracing output issues · ec816087
      Johannes Berg 提交于
      In some cases, e.g. probe_status, there were spaces
      missing so the trace output was confusing. Also make
      it more like mac80211 when printing netdevs/wiphys
      to make reading a combined log easier.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      ec816087
    • J
      mac80211_hwsim: remove printing scan config · a3ad5c3d
      Johannes Berg 提交于
      The frequencies will be printed when actually
      doing the scan, and the IEs can be captured
      on the hwsim0 monitor.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      a3ad5c3d
    • J
      mac80211_hwsim: advertise VHT support · b296005c
      Johannes Berg 提交于
      If the number of channels is > 1, which means that
      hwsim will use mac80211 channel contexts, it can
      also advertise VHT support.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      b296005c
    • J
      wireless: add definitions for VHT MCS support · 7173a1fa
      Johannes Berg 提交于
      Add definitions for the VHT MCS support values that
      are used to indicate, for each number of streams
      (1 through 8) which MCSes are supported.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      7173a1fa
    • J
      mac80211: support VHT rates in TX info · 8bc83c24
      Johannes Berg 提交于
      To achieve this, limit the number of retries to
      31 (instead of 255) and use the three bits that
      are then free for VHT flags.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8bc83c24
    • J
      mac80211: support drivers reporting VHT RX · 5614618e
      Johannes Berg 提交于
      Add support to mac80211 for having drivers report
      received VHT MCS information.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      5614618e
    • J
      nl80211/cfg80211: add VHT MCS support · db9c64cf
      Johannes Berg 提交于
      Add support for reporting and calculating VHT MCSes.
      
      Note that I'm not completely sure that the bitrate
      calculations are correct, nor that they can't be
      simplified.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      db9c64cf
    • J
      mac80211: convert to channel definition struct · 4bf88530
      Johannes Berg 提交于
      Convert mac80211 (and where necessary, some drivers a
      little bit) to the new channel definition struct.
      
      This will allow extending mac80211 for VHT, which is
      currently restricted to channel contexts since there
      are no drivers using that which makes it easier. As
      I also don't care about VHT for drivers not using the
      channel context API, I won't convert the previous API
      to VHT support.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      4bf88530
    • J
      nl80211/cfg80211: support VHT channel configuration · 3d9d1d66
      Johannes Berg 提交于
      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: NJohannes Berg <johannes.berg@intel.com>
      3d9d1d66
    • J
      cfg80211: pass a channel definition struct · 683b6d3b
      Johannes Berg 提交于
      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: NJohannes Berg <johannes.berg@intel.com>
      683b6d3b
    • J
      nl80211: add documentation for channel type · fe4b3181
      Johannes Berg 提交于
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      fe4b3181
    • J
      cfg80211: remove remain-on-channel channel type · 42d97a59
      Johannes Berg 提交于
      As mwifiex (and mac80211 in the software case) are the
      only drivers actually implementing remain-on-channel
      with channel type, userspace can't be relying on it.
      This is the case, as it's used only for P2P operations
      right now.
      
      Rather than adding a flag to tell userspace whether or
      not it can actually rely on it, simplify all the code
      by removing the ability to use different channel types.
      Leave only the validation of the attribute, so that if
      we extend it again later (with the needed capability
      flag), it can't break userspace sending invalid data.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      42d97a59
    • J
      mac80211: fix managed mode channel flags handling · 028e8da0
      Johannes Berg 提交于
      If ieee80211_prep_channel() decides that HT should be
      disabled (because the HT IEs from the AP were invalid)
      it will set the IEEE80211_STA_DISABLE_HT to not send
      HT capabilities to the AP when associating. If this
      happens during authentication, the flag will be lost
      and we send HT frames, even if the channel config was
      set up for non-HT. This can lead to issues.
      
      Fix this by always resetting the ifmgd flags to zero
      when the channel context is released so that the flag
      resetting in ieee80211_mgd_assoc() isn't necessary.
      
      To make the code a bit easier move the call to release
      the channel in ieee80211_set_disassoc() to the end of
      the function together with the flag resetting (which
      needs to be at the end to avoid timers setting flags.)
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      028e8da0