1. 23 Nov, 2012 5 commits
  2. 21 Nov, 2012 1 commit
  3. 20 Nov, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: fix channel context suspend/reconfig handling · fe5f2559
      Johannes Berg authored
      Sujith reported warnings with suspend/resume due to
      channel contexts. When I looked into it, I realised
      that the code was completely broken as it unassigned
      the channel contexts when suspending, which actually
      means they are destroyed.
      Eliad Peller then pointed out that we also need to
      remove the channel contexts from the driver. When I
      looked into this, I also noticed that the code isn't
      handling the virtual monitor interface correctly (if
      it exists.)
      Fix this by calling just the driver methods (if they
      are implemented) instead of using the channel context
      management code. Also add reconfiguration for the
      virtual monitor interface.
      Reported-by: default avatarSujith Manoharan <sujith@msujith.org>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
  4. 19 Nov, 2012 6 commits
  5. 13 Nov, 2012 1 commit
  6. 12 Nov, 2012 1 commit
  7. 09 Nov, 2012 5 commits
  8. 07 Nov, 2012 7 commits
  9. 06 Nov, 2012 2 commits
  10. 05 Nov, 2012 5 commits
  11. 30 Oct, 2012 6 commits
    • Johannes Berg's avatar
      mac80211: use a counter for remain-on-channel cookie · 50febf6a
      Johannes Berg authored
      Instead of using the pointer which can be re-used
      fairly quickly due to allocator patterns and then
      makes debugging difficult, maintain a counter and
      use its value. Since it's a 64-bit value it can't
      really wrap, but catch that case anyway since it
      most likely points to a bug somewhere.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      mac80211: combine status/drop reporting · 8a2fbedc
      Johannes Berg authored
      The TX status reporting is done for both the
      nl80211 report as well as the socket option.
      The socket option is also reported when an
      skb is dropped to guarantee that the copy in
      the IDR tree is freed and status is reported
      to userspace.
      However, when a frame is dropped, no nl80211
      status is reported. This can cause userspace
      to stop making progress while waiting for a
      status notification.
      Combine the nl80211 and socket option status
      reporting into a new function and call it in
      both places -- when the status comes in from
      the driver and when the skb is dropped.
      While at it, also simplify the code in the
      nl80211 portion a bit.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • Johannes Berg's avatar
      mac80211_hwsim: print per interface TX power · cbc668a7
      Johannes Berg authored
      Just for debugging, print the interface TX
      power whenever it changes.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
    • 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>
    • 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>
    • Johannes Berg's avatar
      nl80211: move "can set channel" check · 71fe96bf
      Johannes Berg authored
      Setting the wdev to NULL when the channel can't be
      set for that interface type (to treat the channel
      setting for the wiphy/monitor) currently works, but
      is confusing in the code if netdev/wdev aren't both
      set/unset in the same way. Move the check whether
      the channel can be set to where it's needed so that
      wdev and netdev are always both assigned or NULL.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>