1. 21 9月, 2014 4 次提交
  2. 16 9月, 2014 7 次提交
  3. 15 9月, 2014 9 次提交
  4. 14 9月, 2014 19 次提交
  5. 12 9月, 2014 1 次提交
    • S
      ath9k: Fix beacon miss handling · 167bf96d
      Sujith Manoharan 提交于
      The NoA duration for a GO is half the beacon interval
      and a concurrent context like a STA can be active only
      for that duration, before switching back to the GO's
      operating channel.
      
      Currently, when multiple beacons are missed, the dwell
      time for the STA context is extended to improve the
      chances of receiving a beacon. But the NoA is not updated
      and this will cause problems since the GO is offline
      for a period that is longer than the advertised duration.
      
      Fix this by ensuring that the NoA is updated first before
      extending the time slot for the STA context. Also make
      sure that non-periodic NoA is used for a one-time, longer
      absence period.
      Signed-off-by: NSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      167bf96d