1. 23 8月, 2008 1 次提交
  2. 18 8月, 2008 2 次提交
    • H
      removed unused #include <version.h> · 3eb75aac
      Huang Weiyi 提交于
      The drivers below do not use LINUX_VERSION_CODE nor KERNEL_VERSION.
        drivers/net/wireless/ath5k/base.c
        drivers/net/wireless/b43/main.c
        drivers/net/wireless/ipw2100.c
        drivers/net/wireless/ipw2200.c
        drivers/net/wireless/iwlwifi/iwl-3945.c
        drivers/net/wireless/iwlwifi/iwl-4965.c
        drivers/net/wireless/iwlwifi/iwl-5000.c
        drivers/net/wireless/iwlwifi/iwl-agn.c
        drivers/net/wireless/iwlwifi/iwl-core.c
        drivers/net/wireless/iwlwifi/iwl-eeprom.c
        drivers/net/wireless/iwlwifi/iwl-hcmd.c
        drivers/net/wireless/iwlwifi/iwl-power.c
        drivers/net/wireless/iwlwifi/iwl3945-base.c
      
      This patch removes the said #include <version.h>.
      Signed-off-by: NHuang Weiyi <weiyi.huang@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3eb75aac
    • J
      iwlwifi: fix printk newlines · 6f147926
      Jiri Slaby 提交于
      Add newlines at printk outputs to not break dmesg.
      Signed-off-by: NJiri Slaby <jirislaby@gmail.com>
      Cc: Zhu Yi <yi.zhu@intel.com>
      Cc: Reinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6f147926
  3. 05 8月, 2008 2 次提交
  4. 30 7月, 2008 2 次提交
  5. 15 7月, 2008 2 次提交
  6. 08 7月, 2008 1 次提交
    • A
      iwlwifi: remove input device and fix rfkill state · 80fcc9e2
      Adel Gadllah 提交于
      This patch fixes the iwlwifi rfkill. It removes the input device from iwl3945,
      adds support for RFKILL_STATE_HARD_BLOCKED and calls rfkill_force_state() to
      update the state rather than accessing it directly.
      The calls to iwl|iwl3945_rfkill_set_hw_state() had to be moved because
      rfkill_force_state() cannot be called from an atomic context.
      Tested on iwl3945 and seems to work fine.
      
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Ivo van Doorn <ivdoorn@gmail.com>
      Cc: Fabien Crespel <fcrespel@gmail.com>
      Cc: Zhu Yi <yi.zhu@intel.com>
      Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
      Signed-off-by: NAdel Gadllah <adel.gadllah@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      80fcc9e2
  7. 03 7月, 2008 4 次提交
  8. 01 7月, 2008 2 次提交
  9. 25 6月, 2008 1 次提交
  10. 15 6月, 2008 3 次提交
  11. 04 6月, 2008 2 次提交
  12. 22 5月, 2008 5 次提交
  13. 15 5月, 2008 3 次提交
    • 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
    • B
      iwl3945: do not delay hardware scan if it is a direct scan · 15dbf1b7
      Bill Moss 提交于
      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: NBill Moss <bmoss@CLEMSON.EDU>
      Signed-off-by: NZhu Yi <yi.zhu@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      15dbf1b7
    • A
      iwlwifi : Set monitor mode for 3945 · 5ec03976
      Abhijeet Kolekar 提交于
      The patch leverages mac80211 configure_filter to enable iwl3945
      monitor mode.
      Signed-off-by: NAbhijeet Kolekar <abhijeet.kolekar@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      5ec03976
  14. 08 5月, 2008 4 次提交
  15. 02 5月, 2008 2 次提交
  16. 24 4月, 2008 1 次提交
  17. 17 4月, 2008 1 次提交
  18. 09 4月, 2008 2 次提交