1. 07 Jul, 2008 1 commit
  2. 02 Jul, 2008 1 commit
  3. 14 Jun, 2008 1 commit
    • Harvey Harrison's avatar
      mac80211: add helpers for frame control testing · fd7c8a40
      Harvey Harrison authored
      A few general categories:
      1) ieee80211_has_* tests if particular fctl bits are set, the helpers are de
      in the same order as the fctl defines:
      A combined _has_a4 was also added to test when both FROMDS and TODS are set.
      2) ieee80211_is_* is meant to test whether the frame control is of a certain
      ftype - data, mgmt, ctl, and two special helpers _is_data_qos, _is_data_pres
      which also test a subset of the stype space.
      When testing for a particular stype applicable only to one ftype, functions
      like ieee80211_is_ack have been added.  Note that the ftype is also being
      checked in these helpers.  They have been added for all mgmt and ctl stypes
      in the same order as the STYPE defines.
      3) ieee80211_get_* is meant to take a struct ieee80211_hdr * and returns a
      pointer to somewhere in the struct, see get_SA, get_DA, get_qos_ctl.
      The intel wireless drivers had helpers that used this namespace, convert the
      all to use the new helpers and remove the byteshifting as they were defined
      in cpu-order rather than little-endian.
      Signed-off-by: default avatarHarvey Harrison <harvey.harrison@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  4. 21 May, 2008 2 commits
  5. 14 May, 2008 1 commit
    • 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>
  6. 12 May, 2008 1 commit
  7. 07 May, 2008 1 commit
  8. 29 Apr, 2008 1 commit
  9. 08 Apr, 2008 2 commits
  10. 27 Mar, 2008 1 commit
    • Mohamed Abbas's avatar
      iwlwifi: Add led support · ab53d8af
      Mohamed Abbas authored
      This patch add LEDS support to 3965 and 4965 drivers. It is based on
      led trigger and class. For our drivers we needed to avoid two things.
      1- We receive led trigger on/off on each Rx\Tx frame. In our driver
          we can not call led command like that. In this driver once driver
          receive a start of traffic it call the led command to start blinking
          then we count all bytes of Tx and Rx frame, after two second we count the
          blink rate of last two second then id blink rate changed we call the led
      2- Since we can call led command very often, we make sure we call the
          led command after we receive the statistics notification so
          we don't need to wake up the ucode id it is in sleep state.
          This patch was tested with 4965 and 3945.
      Signed-off-by: default avatarMohamed Abbas <mabbas@linux.intel.com>
      Signed-off-by: Ian Schram<ischram@telenet.be>
      Signed-off-by: default avatarTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  11. 13 Mar, 2008 2 commits
  12. 07 Mar, 2008 5 commits
  13. 06 Mar, 2008 1 commit
  14. 29 Feb, 2008 2 commits
    • Tomas Winkler's avatar
      iwlwifi: Add tx_ant_num hw setting variable · 3e82a822
      Tomas Winkler authored
      Added tx_ant_num variable into hw_setting
      This will be used for scanning TX antenna toggling
      On the way removed ac_queue_num unused
      Signed-off-by: default avatarTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
    • Johannes Berg's avatar
      cfg80211 API for channels/bitrates, mac80211 and driver conversion · 8318d78a
      Johannes Berg authored
      This patch creates new cfg80211 wiphy API for channel and bitrate
      registration and converts mac80211 and drivers to the new API. The
      old mac80211 API is completely ripped out. All drivers (except ath5k)
      are updated to the new API, in many cases I expect that optimisations
      can be done.
      Along with the regulatory code I've also ripped out the
      IEEE80211_HW_DEFAULT_REG_DOMAIN_CONFIGURED flag, I believe it to be
      unnecessary if the hardware simply gives us whatever channels it wants
      to support and we then enable/disable them as required, which is pretty
      much required for travelling.
      Additionally, the patch adds proper "basic" rate handling for STA
      mode interface, AP mode interface will have to have new API added
      to allow userspace to set the basic rate set, currently it'll be
      empty... However, the basic rate handling will need to be moved to
      the BSS conf stuff.
      I do expect there to be bugs in this, especially wrt. transmit
      power handling where I'm basically clueless about how it should work.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  15. 01 Feb, 2008 1 commit
  16. 31 Jan, 2008 1 commit
  17. 28 Jan, 2008 16 commits