1. 24 Sep, 2010 1 commit
  2. 25 Aug, 2010 1 commit
  3. 24 Aug, 2010 1 commit
  4. 28 Jun, 2010 1 commit
  5. 02 Jun, 2010 1 commit
  6. 26 Apr, 2010 1 commit
    • Juuso Oikarinen's avatar
      mac80211: Fix sta->last_tx_rate setting with no-op rate control devices · 0c869808
      Juuso Oikarinen authored
      The sta->last_tx_rate is traditionally updated just before transmitting a
      frame based on information from the rate control algorithm. However, for
      hardware drivers with IEEE80211_HW_HAS_RATE_CONTROL this is not performed,
      as the rate control algorithm is not executed, and because the used rate is
      not known before the frame has actually been transmitted.
      This causes atleast a fixed 1Mb/s to be reported to user space. A few other
      instances of code also rely on this information.
      Fix this by setting the sta->last_tx_rate in tx_status handling. There, look
      for last rates entry set by the driver, and use that as value for
      Signed-off-by: default avatarJuuso Oikarinen <juuso.oikarinen@nokia.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  7. 15 Mar, 2010 1 commit
  8. 15 Feb, 2010 1 commit
    • Jouni Malinen's avatar
      cfg80211/mac80211: allow registering for and sending action frames · 026331c4
      Jouni Malinen authored
      This implements a new command to register for action frames
      that userspace wants to handle instead of the in-kernel
      rejection. It is then responsible for rejecting ones that
      it decided not to handle. There is no unregistration, but
      the socket can be closed for that.
      Frames that are not registered for will not be forwarded
      to userspace and will be rejected by the kernel, the
      cfg80211 API helps implementing that.
      Additionally, this patch adds a new command that allows
      doing action frame transmission from userspace. It can be
      used either to exchange action frames on the current
      operational channel (e.g., with the AP with which we are
      currently associated) or to exchange off-channel Public
      Action frames with the remain-on-channel command.
      Signed-off-by: default avatarJouni Malinen <jouni.malinen@atheros.com>
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  9. 09 Feb, 2010 1 commit
  10. 25 Jan, 2010 1 commit
  11. 19 Jan, 2010 2 commits
  12. 28 Dec, 2009 1 commit
  13. 22 Dec, 2009 1 commit
  14. 21 Dec, 2009 2 commits
    • Johannes Berg's avatar
      mac80211: reduce reliance on netdev · 47846c9b
      Johannes Berg authored
      For bluetooth 3, we will most likely not have
      a netdev for a virtual interface (sdata), so
      prepare for that by reducing the reliance on
      having a netdev. This patch moves the name
      and address fields into the sdata struct and
      uses them from there all over. Some work is
      needed to keep them sync'ed, but that's not
      a lot of work and in slow paths anyway.
      In doing so, this also reduces the number of
      pointer dereferences in many places, because
      of things like sdata->dev->dev_addr becoming
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Johannes Berg's avatar
      mac80211: make station management completely depend on vif · abe60632
      Johannes Berg authored
      The station management currently uses the virtual
      interface, but you cannot add the same station to
      multiple virtual interfaces if you're communicating
      with it in multiple ways.
      This restriction should be lifted so that in the
      future we can, for instance, support bluetooth 3
      with an access point that mac80211 is already
      associated to.
      We can do that by requiring all sta_info_get users
      to provide the virtual interface and making the RX
      code aware that an address may match more than one
      station struct. Thanks to the previous patches this
      one isn't all that large and except for the RX and
      TX status paths changes has low complexity.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  15. 04 Dec, 2009 1 commit
    • Jouni Malinen's avatar
      mac80211: Fix TX status reporting for injected data frames · 914828fa
      Jouni Malinen authored
      An earlier optimization on removing unnecessary traffic on cooked
      monitor interfaces ("mac80211: reduce the amount of unnecessary traffic
      on cooked monitor interfaces ") ended up removing quite a bit more
      than just unnecessary traffic. It was not supposed to remove TX status
      reporting for injected frames, but ended up doing it by checking the
      injected flag in skb->cb only after that field had been cleared with
      memset.. Fix this by taking a local copy of the injected flag before
      skb->cb is cleared.
      This broke user space applications that depend on getting TX status
      notifications for injected data frames. For example, STA inactivity
      poll from hostapd did not work and ended up kicking out stations even
      if they were still present.
      Signed-off-by: default avatarJouni Malinen <j@w1.fi>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  16. 18 Nov, 2009 1 commit