1. 28 3月, 2009 2 次提交
    • L
      b43: fix b43_plcp_get_bitrate_idx_ofdm return type · a3c0b87c
      Lorenzo Nava 提交于
      This patch fixes the return type of b43_plcp_get_bitrate_idx_ofdm. If
      the plcp contains an error, the function return value is 255 instead
      of -1, and the packet was not dropped. This causes a warning in
      __ieee80211_rx function because rate idx is out of range.
      
      Cc: stable@kernel.org
      Signed-off-by: NLorenzo Nava <navalorenx@gmail.com>
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      a3c0b87c
    • M
      b43: Mask PHY TX error interrupt, if not debugging · 3e3ccb3d
      Michael Buesch 提交于
      This masks the PHY TX error interrupt, if debugging is disabled.
      
      Currently we have a bug somewhere which triggers this interrupt once
      in a while. (Depends on the network noise/quality). While this is nonfatal,
      it scares the hell out of users and we frequently receive bugreports
      that incorrectly identify this error message as the reason.
      
      There's another problem with this. The PHY TX error interrupt is protected
      with a watchdog that will restart the device if it keeps triggering very often.
      This is used to fix interrupt storms from completely broken devices.
      
      However, this watchdog might trigger in completely normal operation.
      If the TX capacity of the card is saturated, the likeliness of the watchdog
      triggering increases, as more TX errors occur. The current threshold
      for the watchdog is 1000 errors in 15 seconds.
      
      This patch adds a workaround for the issue by just enabling the interrupt
      if debugging is disabled (by Kconfig or by modparam).
      
      This has the downside that real fatal PHY TX errors are not caught anymore.
      But this is nonfatal due to the following reasons:
      * If the card is not able to transmit anymore, MLME will notice anyway.
      * I did _never_ see a real fatal PHY TX error in a mainline b43 driver.
      * It does _not_ result in interrupt storms or something like that.
        It will simply result in a stalled card. It can be debugged by enabling
        the debugging module parameter.
      Signed-off-by: NMichael Buesch <mb@bu3sch>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3e3ccb3d
  2. 06 3月, 2009 2 次提交
  3. 28 2月, 2009 17 次提交
  4. 18 2月, 2009 1 次提交
  5. 12 2月, 2009 1 次提交
  6. 10 2月, 2009 5 次提交
  7. 30 1月, 2009 12 次提交