1. 26 Nov, 2012 3 commits
  2. 21 Nov, 2012 1 commit
  3. 19 Nov, 2012 4 commits
  4. 13 Nov, 2012 1 commit
  5. 12 Nov, 2012 1 commit
  6. 09 Nov, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: clarify interface iteration and make it configurable · 8b2c9824
      Johannes Berg authored
      
      
      During hardware restart, all interfaces are iterated even
      though they haven't been re-added to the driver, document
      this behaviour. The same also happens during resume, which
      is even more confusing since all of the interfaces were
      previously removed from the driver. Make this optional so
      drivers relying on the current behaviour can still use it,
      but to let drivers that don't want this behaviour disable
      it.
      
      Also convert all API users, keeping the old semantics
      except in hwsim, where the new normal ones are desired.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8b2c9824
    • Johannes Berg's avatar
      mac80211: call driver method when restart completes · 9214ad7f
      Johannes Berg authored
      
      
      When the driver requests a restart (reconfiguration) it
      gets all the normal method calls, but can't really tell
      why they're happening. Call a new restart_complete op
      in the driver when the restart completes, so it could
      keep its own state about the restart and clear it there.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9214ad7f
  7. 06 Nov, 2012 2 commits
  8. 05 Nov, 2012 3 commits
  9. 30 Oct, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: handle TX power per virtual interface · 1ea6f9c0
      Johannes Berg authored
      
      
      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: default avatarJohannes Berg <johannes.berg@intel.com>
      1ea6f9c0
    • Johannes Berg's avatar
      cfg80211: allow per interface TX power setting · c8442118
      Johannes Berg authored
      
      
      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: default avatarJohannes Berg <johannes.berg@intel.com>
      c8442118
  10. 28 Oct, 2012 1 commit
  11. 26 Oct, 2012 8 commits
  12. 23 Oct, 2012 1 commit
  13. 19 Oct, 2012 7 commits
  14. 18 Oct, 2012 4 commits