1. 01 5月, 2010 3 次提交
  2. 17 4月, 2010 7 次提交
  3. 10 4月, 2010 1 次提交
  4. 03 4月, 2010 1 次提交
  5. 01 4月, 2010 1 次提交
    • S
      iwlwifi: manage QoS by mac stack · e61146e3
      Stanislaw Gruszka 提交于
      We activate/deactivate QoS and setup default queue parameters in iwlwifi
      driver. Mac stack do the same, so we do not need repeat that work here.
      Stack also will tell when disable QoS, this will fix driver when working
      with older APs, that do not have QoS implemented.
      
      Patch make "force = true" in iwl_active_qos() assuming we always want
      to do with QoS what mac stack wish.
      
      Patch also remove unused qos_cap bits, do not initialize qos_active = 0,
      as we have it initialized to zero by kzalloc.
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e61146e3
  6. 31 3月, 2010 2 次提交
  7. 20 3月, 2010 3 次提交
    • W
      iwlwifi: Recover TX flow stall due to stuck queue · b74e31a9
      Wey-Yi Guy 提交于
      Monitors the internal TX queues periodically.  When a queue is stuck
      for some unknown conditions causing the throughput to drop and the
      transfer is stop, the driver will force firmware reload and bring the
      system back to normal operational state.
      
      The iwlwifi devices behave differently in this regard so this feature is
      made part of the ops infrastructure so we can have more control on how to
      monitor and recover from tx queue stall case per device.
      Signed-off-by: NTrieu 'Andrew' Nguyen <trieux.t.nguyen@intel.com>
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      b74e31a9
    • R
      iwlwifi: implement new mac80211 station add/remove calls · fe6b23dd
      Reinette Chatre 提交于
      mac80211 recently implemented two new callbacks that are used to request
      station add/remove from the driver. The benefot from these new callbacks
      are that they enable the driver to sleep while performing this work.
      
      This is a big patch since a few things need to be coordinated in this move.
      First we need to decouple station management from rate scaling, which
      caused a lot of code to be moved and/or deleted. Next we needed to tie in
      with mac80211's station management callback and let it direct our station
      management as well as trigger the rate scaling initialization.
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      fe6b23dd
    • R
      iwlwifi: only add broadcast station once · 7e246191
      Reinette Chatre 提交于
      Currently the broadcast station is added after every RXON command. Change
      this to only add the broadcast station when interface is added by mac80211.
      With this we need some extra work to ensure broadcast station is always
      present since station table is cleared when RXON without ASSOC bit set is
      sent. To deal with this we re-add all driver known stations to uCode after
      such an RXON command is sent.
      
      We also do some cleanup and remove the various calls to clear the station
      table. We now only clear the station table in two scenarios:
      - only clear uCode portion of station table when RXON command without ASSOC
      bit is sent
      - clear uCode and driver portion when interface goes down or is removed.
      
      We need to do this clearing when interface goes down to deal with the
      device restart/reconfigure routines which do not remove the interface, but
      do add the interface during reconfiguration.
      
      Previously the keys were also cleared when station table in driver is
      cleared, this is not done anymore since mac80211 will take care that keys
      are set and cleared correctly.
      
      There is a known issue with this change. Associating with different AP
      without bringing interface down fails with a firmware error. This is
      because of the lack of full station notification support and the later
      patches in this series that complete the station notification support will
      fix this.
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      7e246191
  8. 10 3月, 2010 10 次提交
  9. 20 2月, 2010 2 次提交
  10. 12 2月, 2010 3 次提交
  11. 09 2月, 2010 1 次提交
  12. 30 1月, 2010 1 次提交
  13. 26 1月, 2010 2 次提交
    • R
      iwlwifi: cleanup spectrum measurement command support · 81963d68
      Reinette Chatre 提交于
      In iwlagn the support for spectrum measurement command has been
      disabled since v2.6.29 without any requests for it. In addition to this
      when this command is indeed enabled it has been found to trigger firmware
      SYSASSERT on at least 4965 and 5100 hardware (see
      http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1952 ). Since then
      this code has been bitrotting and cannot just be enabled without porting.
      
      Remove support for spectrum measurement command from iwlagn. It can be
      added back if there is a future need and the firmware problem it triggers
      has been fixed. Support for the spectrim measurement notification remains
      as it has been enabled all the time.
      
      In addition to this remove the 3945 spectrum measurement command Kconfig
      option and make this command always supported. The code added by this
      enabling is minimal and only run when user triggers a spectrum measurement
      request via sysfs.
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      81963d68
    • W
      iwlwifi: configure missed beacon threshold · a13d276f
      Wey-Yi Guy 提交于
      Add support to configure missed beacon threshold, by default, if receive
      "missed beacon" notification from uCode and has more than 5 consecutive
      beacon missed, then perform sensitivity calibration; with this change,
      allow user to adjust the missed beacon threshold from debugfs in case
      more sensitivity calibration required for better performance in noisy
      environment
      
      The default value (=5) should be good enough for the normal condition,
      but for very noisy environment, more sensitivity calibration could help
      improve the throughput, so by setting the missed beacon threshold to
      lower number, user might experience better performance result.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      a13d276f
  14. 20 1月, 2010 2 次提交
  15. 29 12月, 2009 1 次提交