1. 04 Dec, 2009 5 commits
    • Michael Buesch's avatar
      airo: Fix integer overflow warning · 1f351e38
      Michael Buesch authored
      
      
      On BigEndian gcc complains:
      
      drivers/net/wireless/airo.c: In function ‘sniffing_mode’:
      drivers/net/wireless/airo.c:4809: warning: integer overflow in expression
      
      Fix this by doing the bitwise AND on the host-endian value.
      
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      1f351e38
    • Gertjan van Wingerde's avatar
      rt2x00: Fix padding bug on L2PAD devices. · a5186e99
      Gertjan van Wingerde authored
      
      
      While reviewing the l2pad function to align both the header and the payload
      on a DMA-capable boundary a bug was discovered where the payload would not
      be properly aligned. The header_align value was used where the payload_align
      value should have been used.
      
      Signed-off-by: default avatarGertjan van Wingerde <gwingerde@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      a5186e99
    • Jean Tourrilhes's avatar
      WE: Fix set events not propagated · 1014eb6e
      Jean Tourrilhes authored
      
      
      I've just noticed that some events are no longer propagated
      for some wireless drivers. Basically, SET request with a extra payload
      for driver without commit handler. The fix is pretty simple, see
      attached.
      	Actually, a few lines below this line, you will see that the
      event generation for simple SET (iwpoint-less ?) is done properly,
      and this other event generation does not need fixing.
      
      Signed-off-by: default avatarJean Tourrilhes <jt@hpl.hp.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      1014eb6e
    • Larry Finger's avatar
      b43legacy: avoid PPC fault during resume · 316a4d96
      Larry Finger authored
      
      
      For PPC architecture with PHY Revision < 3, a read of the register
      B43_MMIO_HWENABLED_LO will cause a CPU fault unless b43legacy_status()
      returns a value of 2 (B43legacy_STAT_STARTED); however, one finds that
      the driver is unable to associate after resuming from hibernation unless
      this routine returns 1. To satisfy both conditions, the routine is rewritten
      to return TRUE whenever b43legacy_status() returns a value < 2.
      
      This patch fixes the second problem listed in the postings for Red Hat
      Bugzilla #538523.
      
      Signed-off-by: default avatarLarry Finger <Larry.Finger@lwfinger.net>
      Cc: Stable <stable@vger.org>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      316a4d96
    • Larry Finger's avatar
      b43: avoid PPC fault during resume · c2ff581a
      Larry Finger authored
      
      
      The routine b43_is_hw_radio_enabled() has long been a problem.
      For PPC architecture with PHY Revision < 3, a read of the register
      B43_MMIO_HWENABLED_LO will cause a CPU fault unless b43_status()
      returns a value of 2 (B43_STAT_STARTED) (BUG 14181). Fixing that
      results in Bug 14538 in which the driver is unable to reassociate
      after resuming from hibernation because b43_status() returns 0.
      
      The correct fix would be to determine why the status is 0; however,
      I have not yet found why that happens. The correct value is found for
      my device, which has PHY revision >= 3.
      
      Returning TRUE when the PHY revision < 3 and b43_status() returns 0 fixes
      the regression for 2.6.32.
      
      This patch fixes the problem in Red Hat Bugzilla #538523.
      
      Signed-off-by: default avatarLarry Finger <Larry.Finger@lwfinger.net>
      Tested-by: default avatarChristian Casteyde <casteyde.christian@free.fr>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      c2ff581a
  2. 28 Nov, 2009 35 commits