1. 06 Oct, 2010 1 commit
  2. 05 Oct, 2010 9 commits
  3. 28 Sep, 2010 2 commits
    • Juuso Oikarinen's avatar
      mac80211: Fix WMM driver queue configuration · f2176d72
      Juuso Oikarinen authored
      The WMM parameter configuration function (ieee80211_sta_wmm_params) only
      configures the WMM parameters to the driver is the wmm_last_param_set
      counter value is changed by the AP.
      The wmm_last_param_set is initialized to -1 on association in order to ensure
      the configuration is made to the driver at least once on association, but
      currently this initialization is done *after* the WMM parameter configuration
      function was called.
      This leads to unreliability in the driver getting properly configured on first
      association (depending on what counter value the AP happens to use.) When
      disassociating (the wmm default parameters are configured to the driver) and
      then reassociating, due to the above the WMM configuration is not set to the
      driver at all.
      On drivers without beacon filtering the problem is corrected by later beacons,
      but on drivers with beacon filtering the WMM will remain permanently incorrectly
      Fix this by moving the initialization of wmm_last_param_set to -1 before
      ieee80211_sta_wmm_params is called on association.
      Signed-off-by: default avatarJuuso Oikarinen <juuso.oikarinen@nokia.com>
      Acked-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Luis R. Rodriguez's avatar
      mac80211: fix offchannel assumption upon association · 8d4780eb
      Luis R. Rodriguez authored
      Association is dealt with as an atomic offchannel operation,
      we do this because we don't know we are associated until we
      get the associatin response from the AP. When we do get the
      associatin response though we were never clearing the offchannel
      state. This has a few implications, we told drivers we were
      still offchannel, and the first configured TX power for the
      channel does not take into account any power constraints.
      For ath9k this meant ANI calibration would not start upon
      association, and we'd have to wait until the first bgscan
      to be triggered. There may be other issues this resolves
      but I'm too lazy to comb the code to check.
      Cc: stable@kernel.org
      Cc: Amod Bodas <amod.bodas@atheros.com>
      Cc: Vasanth Thiagarajan <vasanth.thiagarajan@atheros.com>
      Signed-off-by: default avatarLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  4. 27 Sep, 2010 9 commits
  5. 24 Sep, 2010 4 commits
  6. 16 Sep, 2010 10 commits
  7. 14 Sep, 2010 3 commits
  8. 01 Sep, 2010 1 commit
  9. 31 Aug, 2010 1 commit