1. 26 11月, 2013 1 次提交
  2. 23 8月, 2013 1 次提交
    • J
      mac80211: move setting WIPHY_FLAG_SUPPORTS_SCHED_SCAN into drivers · 1fb90260
      Johannes Berg 提交于
      mac80211 currently sets WIPHY_FLAG_SUPPORTS_SCHED_SCAN based on whether
      the start_sched_scan operation is supported or not, but that will not
      be correct for all drivers, we're adding scheduled scan to the iwlmvm
      driver but it depends on firmware support.
      
      Therefore, move setting WIPHY_FLAG_SUPPORTS_SCHED_SCAN into the drivers
      so that they can control it regardless of implementing the operation.
      
      This currently only affects the TI drivers since they're the only ones
      implementing scheduled scan (in a mac80211 driver.)
      Acked-by: NLuciano Coelho <luca@coelho.fi>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      1fb90260
  3. 16 7月, 2013 2 次提交
  4. 04 7月, 2013 1 次提交
  5. 04 6月, 2013 1 次提交
  6. 25 5月, 2013 1 次提交
    • J
      cfg80211/mac80211: use cfg80211 wdev mutex in mac80211 · 8d61ffa5
      Johannes Berg 提交于
      Using separate locks in cfg80211 and mac80211 has always
      caused issues, for example having to unlock in places in
      mac80211 to call cfg80211, which even needed a framework
      to make cfg80211 calls after some functions returned etc.
      
      Additionally, I suspect some issues people have reported
      with the cfg80211 state getting confused could be due to
      such issues, when cfg80211 is asking mac80211 to change
      state but mac80211 is in the process of telling cfg80211
      that the state changed (in another way.)
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8d61ffa5
  7. 16 4月, 2013 1 次提交
  8. 08 4月, 2013 1 次提交
  9. 26 3月, 2013 1 次提交
  10. 25 3月, 2013 1 次提交
  11. 19 3月, 2013 1 次提交
  12. 11 3月, 2013 1 次提交
  13. 07 3月, 2013 1 次提交
    • J
      mac80211: provide ieee80211_sta_eosp() · e943789e
      Johannes Berg 提交于
      The irqsafe version ieee80211_sta_eosp_irqsafe() exists, but
      drivers must not mix calls to any irqsafe/non-irqsafe function.
      Both ath9k and iwlwifi, the likely first users of this interface,
      use non-irqsafe RX/TX/TX status so must also use a non-irqsafe
      version of this function. Since no driver uses the _irqsafe()
      version, remove that.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      e943789e
  14. 06 3月, 2013 3 次提交
  15. 28 2月, 2013 1 次提交
  16. 15 2月, 2013 4 次提交
  17. 12 2月, 2013 2 次提交
  18. 19 1月, 2013 2 次提交
  19. 03 1月, 2013 5 次提交
  20. 30 11月, 2012 1 次提交
  21. 27 11月, 2012 1 次提交
  22. 26 11月, 2012 2 次提交
    • 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
      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
  23. 09 11月, 2012 1 次提交
  24. 30 10月, 2012 1 次提交
    • J
      mac80211: handle TX power per virtual interface · 1ea6f9c0
      Johannes Berg 提交于
      Even before channel contexts/multi-channel, having a
      single global TX power limit was already problematic,
      in particular if two managed interfaces connected to
      two APs with different power constraints. The channel
      context introduction completely broke this though and
      in fact I had disabled TX power configuration there
      for drivers using channel contexts.
      
      Change everything to track TX power per interface so
      that different user settings and different channel
      maxima are treated correctly. Also continue tracking
      the global TX power though for compatibility with
      applications that attempt to configure the wiphy's
      TX power globally.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      1ea6f9c0
  25. 22 10月, 2012 1 次提交
  26. 18 10月, 2012 2 次提交