1. 01 11月, 2008 2 次提交
  2. 28 10月, 2008 1 次提交
  3. 13 10月, 2008 1 次提交
    • I
      net/mac80211/rx.c: fix build error · bf94e17b
      Ingo Molnar 提交于
      older versions of gcc do not recognize that ieee80211_rx_h_mesh_fwding()
      is unused when CONFIG_MAC80211_MESH is disabled:
      
        net/built-in.o: In function `ieee80211_rx_h_mesh_fwding':
        rx.c:(.text+0xd89af): undefined reference to `mpp_path_lookup'
        rx.c:(.text+0xd89c6): undefined reference to `mpp_path_add'
      
      as this code construct:
      
              if (ieee80211_vif_is_mesh(&sdata->vif))
                      CALL_RXH(ieee80211_rx_h_mesh_fwding);
      
      still causes ieee80211_rx_h_mesh_fwding() to be linked in.
      
      Protect these places with an #ifdef.
      
      commit b0dee578 ("Fix modpost failure when rx handlers are not inlined.")
      solved part of this problem - this patch is still needed.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bf94e17b
  4. 01 10月, 2008 1 次提交
  5. 25 9月, 2008 3 次提交
  6. 16 9月, 2008 6 次提交
  7. 12 9月, 2008 3 次提交
  8. 09 9月, 2008 1 次提交
    • E
      mac80211: Fix rate scale initialization in IBSS · 8e1535d5
      Emmanuel Grumbach 提交于
      This patch address some IBSS rate issues introduced or not covered
      by "mac80211: eliminate IBSS warning in rate_lowest_index()" and
      "cfg80211 API for channels/bitrates, mac80211 and driver conversion".
      
      This patch:
      1. Moves addition of IBSS station from
      prepare_for_handlers to ieee80211_rx_bss_info when triggered from beacon
      eliminating bogus supported rates.
      2. Initialize properly supported rates also in IBSS merging
      3. Ensure that mandatory rates are always added into supported
      rates. This is needed in case when station addition is triggered from
      non beacon/probe packet. Some management frames need to be sent
      4. Remove initialization of supported rates from self rates. This path
      was dead code after 6bc37c06bc4 and in general incorrect.
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Cc: Vladimir Koutny <vlado@work.ksp.sk>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      8e1535d5
  9. 23 8月, 2008 6 次提交
  10. 07 8月, 2008 1 次提交
  11. 15 7月, 2008 3 次提交
  12. 09 7月, 2008 2 次提交
  13. 03 7月, 2008 2 次提交
  14. 27 6月, 2008 1 次提交
  15. 15 6月, 2008 2 次提交
  16. 29 5月, 2008 1 次提交
  17. 22 5月, 2008 2 次提交
  18. 15 5月, 2008 2 次提交
    • B
      mac80211: make rx radiotap header more flexible · 601ae7f2
      Bruno Randolf 提交于
      use hw flags and rx flags to determine which fields are present in the header
      and use all available information from the driver.
      
      make sure radiotap header starts at a naturally aligned address (mod 8) for
      all radiotap fields.
      Signed-off-by: NBruno Randolf <br1@einfach.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      601ae7f2
    • 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