1. 13 6月, 2013 4 次提交
  2. 12 6月, 2013 1 次提交
  3. 18 5月, 2013 1 次提交
  4. 17 5月, 2013 1 次提交
  5. 09 5月, 2013 1 次提交
    • S
      iwl4965: workaround connection regression on passive channel · dd9c4640
      Stanislaw Gruszka 提交于
      Jake reported that since commit 1672c0e3
      "mac80211: start auth/assoc timeout on frame status", he is unable to
      connect to his AP, which is configured to use passive channel.
      
      After switch to passive channel 4965 firmware drops any TX packet until
      it receives beacon. Before commit 1672c0e3 we waited on channel and
      retransmit packet after 200ms, that makes we receive beacon on the
      meantime and association process succeed. New mac80211 behaviour cause
      that any ASSOC frame fail immediately on iwl4965 and we can not
      associate.
      
      This patch restore old mac80211 behaviour for iwl4965, by removing
      IEEE80211_HW_REPORTS_TX_ACK_STATUS feature. This feature will be
      added again to iwl4965 driver, when different, more complex
      workaround for this firmware issue, will be added to the driver.
      
      Cc: stable@vger.kernel.org # 3.9
      Bisected-by: NJake Edge <jake@lwn.net>
      Reported-and-tested-by: NJake Edge <jake@lwn.net>
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      dd9c4640
  6. 16 4月, 2013 1 次提交
    • J
      mac80211: support secondary channel offset in CSA · 85220d71
      Johannes Berg 提交于
      Add support for the secondary channel offset IE in channel
      switch announcements. This is necessary for proper handling
      of CSA on HT access points.
      
      For this to work it is also necessary to convert everything
      here to use chandef structs instead of just channels. The
      driver updates aren't really correct though. In particular,
      the TI wl18xx driver update can't possibly be right since
      it just ignores the new channel width for lack of firmware
      API.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      85220d71
  7. 27 3月, 2013 2 次提交
  8. 26 3月, 2013 1 次提交
  9. 19 3月, 2013 2 次提交
  10. 18 3月, 2013 1 次提交
  11. 15 3月, 2013 1 次提交
  12. 12 3月, 2013 1 次提交
  13. 06 3月, 2013 1 次提交
  14. 15 2月, 2013 2 次提交
  15. 02 2月, 2013 2 次提交
  16. 31 1月, 2013 4 次提交
  17. 23 1月, 2013 2 次提交
  18. 08 1月, 2013 3 次提交
  19. 03 1月, 2013 1 次提交
    • J
      mac80211: split TX aggregation stop action · 18b559d5
      Johannes Berg 提交于
      When TX aggregation is stopped, there are a few
      different cases:
       - connection with the peer was dropped
       - session stop was requested locally
       - session stop was requested by the peer
       - connection was dropped while a session is stopping
      
      The behaviour in these cases should be different, if
      the connection is dropped then the driver should drop
      all frames, otherwise the frames may continue to be
      transmitted, aggregated in the case of a locally
      requested session stop or unaggregated in the case of
      the peer requesting session stop.
      
      Split these different cases so that the driver can
      act accordingly; however, treat local and remote stop
      the same way and ask the driver to not send frames as
      aggregated packets any more.
      
      In the case of connection drop, the stop callback the
      driver is otherwise supposed to call is no longer
      required.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      18b559d5
  20. 08 12月, 2012 2 次提交
  21. 07 12月, 2012 1 次提交
  22. 27 11月, 2012 1 次提交
  23. 15 11月, 2012 1 次提交
  24. 14 11月, 2012 1 次提交
  25. 25 9月, 2012 1 次提交
  26. 24 8月, 2012 1 次提交