1. 01 11月, 2008 2 次提交
  2. 28 10月, 2008 1 次提交
  3. 15 5月, 2008 1 次提交
    • B
      mac80211: use hardware flags for signal/noise units · 566bfe5a
      Bruno Randolf 提交于
      trying to clean up the signal/noise code. the previous code in mac80211 had
      confusing names for the related variables, did not have much definition of
      what units of signal and noise were provided and used implicit mechanisms from
      the wireless extensions.
      
      this patch introduces hardware capability flags to let the hardware specify
      clearly if it can provide signal and noise level values and which units it can
      provide. this also anticipates possible new units like RCPI in the future.
      
      for signal:
      
        IEEE80211_HW_SIGNAL_UNSPEC - unspecified, unknown, hw specific
        IEEE80211_HW_SIGNAL_DB     - dB difference to unspecified reference point
        IEEE80211_HW_SIGNAL_DBM    - dBm, difference to 1mW
      
      for noise we currently only have dBm:
      
        IEEE80211_HW_NOISE_DBM     - dBm, difference to 1mW
      
      if IEEE80211_HW_SIGNAL_UNSPEC or IEEE80211_HW_SIGNAL_DB is used the driver has
      to provide the maximum value (max_signal) it reports in order for applications
      to make sense of the signal values.
      
      i tried my best to find out for each driver what it can provide and update it
      but i'm not sure (?) for some of them and used the more conservative guess in
      doubt. this can be fixed easily after this patch has been merged by changing
      the hardware flags of the driver.
      
      DRIVER          SIGNAL    MAX	NOISE   QUAL
      -----------------------------------------------------------------
      adm8211         unspec(?) 100   n/a     missing
      at76_usb        unspec(?) (?)   unused  missing
      ath5k           dBm             dBm     percent rssi
      b43legacy       dBm             dBm     percent jssi(?)
      b43             dBm             dBm     percent jssi(?)
      iwl-3945        dBm             dBm     percent snr+more
      iwl-4965        dBm             dBm     percent snr+more
      p54             unspec    127   n/a     missing
      rt2x00          dBm	        n/a     percent rssi+tx/rx frame success
        rt2400        dBm             n/a
        rt2500pci     dBm             n/a
        rt2500usb     dBm             n/a
        rt61pci       dBm             n/a
        rt73usb       dBm             n/a
      rtl8180         unspec(?) 65    n/a     (?)
      rtl8187         unspec(?) 65    (?)     noise(?)
      zd1211          dB(?)     100   n/a     percent
      
      drivers/net/wireless/ath5k/base.c:      Changes-licensed-under: 3-Clause-BSD
      Signed-off-by: NBruno Randolf <br1@einfach.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      566bfe5a
  4. 09 4月, 2008 1 次提交
    • D
      [NET]: Undo code bloat in hot paths due to print_mac(). · 21f644f3
      David S. Miller 提交于
      If print_mac() is used inside of a pr_debug() the compiler
      can't see that the call is redundant so still performs it
      even of pr_debug() ends up being a nop.
      
      So don't use print_mac() in such cases in hot code paths,
      use MAC_FMT et al. instead.
      
      As noted by Joe Perches, pr_debug() could be modified to
      handle this better, but that is a change to an interface
      used by the entire kernel and thus needs to be validated
      carefully.  This here is thus the less risky fix for
      2.6.25
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      21f644f3
  5. 29 1月, 2008 4 次提交
  6. 11 10月, 2007 1 次提交
  7. 02 10月, 2007 1 次提交
    • J
      [IEEE80211]: avoid integer underflow for runt rx frames · 04045f98
      John W. Linville 提交于
      Reported by Chris Evans <scarybeasts@gmail.com>:
      
      > The summary is that an evil 80211 frame can crash out a victim's
      > machine. It only applies to drivers using the 80211 wireless code, and
      > only then to certain drivers (and even then depends on a card's
      > firmware not dropping a dubious packet). I must confess I'm not
      > keeping track of Linux wireless support, and the different protocol
      > stacks etc.
      >
      > Details are as follows:
      >
      > ieee80211_rx() does not explicitly check that "skb->len >= hdrlen".
      > There are other skb->len checks, but not enough to prevent a subtle
      > off-by-two error if the frame has the IEEE80211_STYPE_QOS_DATA flag
      > set.
      >
      > This leads to integer underflow and crash here:
      >
      > if (frag != 0)
      >    flen -= hdrlen;
      >
      > (flen is subsequently used as a memcpy length parameter).
      
      How about this?
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      04045f98
  8. 28 4月, 2007 1 次提交
  9. 26 4月, 2007 9 次提交
  10. 11 2月, 2007 1 次提交
  11. 02 12月, 2006 3 次提交
  12. 01 11月, 2006 1 次提交
  13. 30 8月, 2006 1 次提交
  14. 28 7月, 2006 2 次提交
  15. 06 7月, 2006 2 次提交
  16. 01 7月, 2006 1 次提交
  17. 25 4月, 2006 2 次提交
  18. 23 3月, 2006 1 次提交
  19. 18 3月, 2006 1 次提交
    • J
      [PATCH] ieee80211: Don't update network statistics from off-channel packets. · f44349f2
      James Ketrenos 提交于
      This patch fixes a problem in the ieee80211 probe response and beacon
      reception code that would use the packet statistics for a network even
      if they were received on a channel other than that which the network
      exists on.
      
      This causes a problem in overlapping channels where, for example, a
      strong AP on channel 2 could have its beacons received on channels 1 and
      3, but at much lower signal levels.  If scanning was done sequentially,
      this means the beacon received on channel 3 would update the AP's signal
      level as being much lower than it really is, which subsequently could
      cause that AP to be passed over and an alternate AP selected.
      Signed-off-by: NJames Ketrenos <jketreno@linux.intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f44349f2
  20. 16 3月, 2006 1 次提交
  21. 28 2月, 2006 1 次提交
  22. 31 1月, 2006 2 次提交