1. 19 9月, 2012 1 次提交
  2. 25 6月, 2012 1 次提交
    • J
      iwlwifi: limit dwell time more strictly · b3a6d2e0
      Johannes Berg 提交于
      The dwell time for scanning is currently limited
      so that it fits into the timings inside the ucode
      when that is tracking DTIM/beacon periods for the
      AP(s) it's connected to.
      
      However, when it's connected to two APs, those
      may be in lockstep, for example if they both have
      a DTIM interval of 100 TU, then one could be 50
      TU after the other, leaving only 50 TU free to
      be used by scanning.
      
      Since we can't know how far apart they are the
      only option is to restrict to 1/2 of the minium
      of the two APs.
      
      In theory, it would be possible to not use 1/2 of
      the minimum but take into account that if they
      have different intervals then there will be a bit
      more time since they can't be in lockstep, but as
      they will have 100 TU intervals in practice that
      complex calculation will probably just result in
      hard-to-find bugs.
      Reviewed-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      b3a6d2e0
  3. 21 6月, 2012 1 次提交
  4. 20 6月, 2012 1 次提交
  5. 06 6月, 2012 6 次提交
  6. 17 5月, 2012 3 次提交
  7. 24 4月, 2012 1 次提交
  8. 18 4月, 2012 1 次提交
  9. 13 4月, 2012 1 次提交
  10. 10 4月, 2012 5 次提交
  11. 09 3月, 2012 1 次提交
  12. 08 3月, 2012 4 次提交
  13. 07 3月, 2012 3 次提交
  14. 18 2月, 2012 1 次提交
  15. 31 1月, 2012 1 次提交
  16. 29 1月, 2012 1 次提交
  17. 25 1月, 2012 1 次提交
  18. 17 1月, 2012 1 次提交
  19. 07 1月, 2012 1 次提交
  20. 16 12月, 2011 1 次提交
  21. 12 11月, 2011 2 次提交
  22. 09 11月, 2011 1 次提交
  23. 15 10月, 2011 1 次提交