1. 14 Jun, 2008 3 commits
  2. 03 Jun, 2008 2 commits
  3. 21 May, 2008 5 commits
  4. 14 May, 2008 3 commits
    • Bruno Randolf's avatar
      mac80211: use hardware flags for signal/noise units · 566bfe5a
      Bruno Randolf authored
      
      
      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: default avatarBruno Randolf <br1@einfach.org>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      566bfe5a
    • Bill Moss's avatar
      iwl3945: do not delay hardware scan if it is a direct scan · 15dbf1b7
      Bill Moss authored
      
      
      iwl3945 <---> mac80211 <----> wpa_supplicant <---> NetworkManager
      
      When a hardware scan is completed and another scan is requested in less
      than two seconds, iwlwifi will not do the second scan and will pass the
      error code -EAGAIN back to mac80211 where it quickly dies. The error
      code is not passed along to the calling program wpa_supplicant. After a
      timeout, wpa_supplicant will just give up but it will not know why the
      scan failed. This is a weakness in the design.
      
      I ran into this issue when I was trying to figure out why it takes more
      an a minute for NetworkManager to connect after Networking has been
      disabled and then re-enabled. I found a good deal of unnecessary work
      being done because mac80211 requests authentication when the interface
      is not configured, the ANY mode. I created an experimental passive
      (NOTANY) mode for mac80211 to eliminate this case. Then NetworkManager
      became so fast that I ran into the iwlwifi 2 second delay next scan
      issue which we are discussing.
      
      The patch resolves the problem by bypassing the delay if the scan request
      is a direct scan. It should do less harm to the hardware.
      Signed-off-by: default avatarBill Moss <bmoss@CLEMSON.EDU>
      Signed-off-by: default avatarZhu Yi <yi.zhu@intel.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      15dbf1b7
    • Abhijeet Kolekar's avatar
      iwlwifi : Set monitor mode for 3945 · 5ec03976
      Abhijeet Kolekar authored
      
      
      The patch leverages mac80211 configure_filter to enable iwl3945
      monitor mode.
      Signed-off-by: default avatarAbhijeet Kolekar <abhijeet.kolekar@intel.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      5ec03976
  5. 07 May, 2008 4 commits
  6. 01 May, 2008 2 commits
  7. 23 Apr, 2008 1 commit
  8. 16 Apr, 2008 1 commit
  9. 08 Apr, 2008 3 commits
  10. 01 Apr, 2008 3 commits
  11. 27 Mar, 2008 3 commits
  12. 24 Mar, 2008 2 commits
  13. 13 Mar, 2008 2 commits
  14. 07 Mar, 2008 6 commits