1. 24 10月, 2012 8 次提交
  2. 18 10月, 2012 2 次提交
    • A
      wireless: drivers: make use of WLAN_EID_VENDOR_SPECIFIC · 04b2312a
      Arend van Spriel 提交于
      The include file linux/ieee80211.h contains three definitions for
      the same thing in enum ieee80211_eid due to historic changes:
      
      /* Information Element IDs */
      enum ieee80211_eid {
          :
          WLAN_EID_WPA = 221,
          WLAN_EID_GENERIC = 221,
          WLAN_EID_VENDOR_SPECIFIC = 221,
          :
      };
      
      The standard refers to this as "vendor specific" element so the
      other two definitions are better not used. This patch changes the
      wireless drivers to use one definition, ie. WLAN_EID_VENDOR_SPECIFIC.
      
      Cc: Jouni Malinen <j@w1.fi>
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Larry Finger <Larry.Finger@lwfinger.net>
      Acked-by: Kalle Valo <kvalo@qca.qualcomm.com> [ath6kl]
      Acked-by: Bing Zhao <bzhao@marvell.com> [mwifiex]
      Acked-by: Stanislav Yakovlev <stas.yakovlev@gmail.com> [ipw2x00]
      Signed-off-by: NArend van Spriel <arend@broadcom.com>
      [change libipw as well]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      04b2312a
    • J
      wireless: use OR operation to set wiphy features · b292219f
      Johannes Berg 提交于
      The next patch will introduce a flag that is set
      by default in cfg80211 so drivers and mac80211
      need to use |= to set features they have so that
      they don't clear the already-set feature.
      
      We could set the flag in wiphy_register() instead
      of wiphy_new() to avoid this patch, but then the
      drivers couldn't *unset* flags they don't want to
      use even though the implementation is generic.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      b292219f
  3. 19 9月, 2012 1 次提交
  4. 12 7月, 2012 2 次提交
  5. 09 7月, 2012 1 次提交
    • J
      cfg80211: use wdev in mgmt-tx/ROC APIs · 71bbc994
      Johannes Berg 提交于
      The management frame and remain-on-channel APIs will be
      needed in the P2P device abstraction, so move them over
      to the new wdev-based APIs. Userspace can still use both
      the interface index and wdev identifier for them so it's
      backward compatible, but for the P2P Device wdev it will
      be able to use the wdev identifier only.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      71bbc994
  6. 27 6月, 2012 1 次提交
  7. 14 6月, 2012 1 次提交
  8. 11 6月, 2012 5 次提交
  9. 06 6月, 2012 1 次提交
    • J
      cfg80211: provide channel to start_ap function · aa430da4
      Johannes Berg 提交于
      Instead of setting the channel first and then
      starting the AP, let cfg80211 store the channel
      and provide it as one of the AP settings.
      
      This means that now you have to set the channel
      before you can start an AP interface, but since
      hostapd/wpa_supplicant always do that we're OK
      with this change.
      
      Alternatively, it's now possible to give the
      channel as an attribute to the start-ap nl80211
      command, overriding any preset channel.
      
      Cc: Kalle Valo <kvalo@qca.qualcomm.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      aa430da4
  10. 30 5月, 2012 1 次提交
    • K
      ath6kl: separate ht cap for each band · 67b3f129
      Kiran Reddy 提交于
      In virtual interface structure, for each band separate ht cap
      is needed. so that one can disable or enable ht capability band
      wise.
      This will fix the following issue:
      
      1) Disable 11n from supplicant and start a P2P GO.
      2) In beacon frames no HT-CAP IE is seen which is expected.
      3) Now remove the P2P GO and kill the supplicant.
      4) Beacon stops
      5) Now using iw  associate to an external AP in 5 GHZ
      6) In 5 GHZ no HT IE going in assoc request but
      when  associated in 2.4 GHZ can see HT IES over the air
      in assoc request.
      
      In the code for del_beacon in cfg80211.c,set_ht_cap is being
      called first for 2.4 GHZ and then for 5 GHZ. When  called
      for the first time for 2.4 GHZ the enable flag will be set to true
      and so when called for the second time for 5 GHZ it just returns
      after checking the flag.
      
      Also using this one can have different HT capabilities
      per band (for example one may decide not to use 20/40 in 2.4 GHZ
      but use it in 5 GHZ). So maintaining a single context is not ok.
      it is true for even the enable/disable flag and other HT
      capabilities as well
      Signed-off-by: NKiran Reddy <c_lreddy@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      67b3f129
  11. 29 5月, 2012 2 次提交
  12. 24 5月, 2012 2 次提交
  13. 19 5月, 2012 1 次提交
    • S
      USB: Disable hub-initiated LPM for comms devices. · e1f12eb6
      Sarah Sharp 提交于
      Hub-initiated LPM is not good for USB communications devices.  Comms
      devices should be able to tell when their link can go into a lower power
      state, because they know when an incoming transmission is finished.
      Ideally, these devices would slam their links into a lower power state,
      using the device-initiated LPM, after finishing the last packet of their
      data transfer.
      
      If we enable the idle timeouts for the parent hubs to enable
      hub-initiated LPM, we will get a lot of useless LPM packets on the bus
      as the devices reject LPM transitions when they're in the middle of
      receiving data.  Worse, some devices might blindly accept the
      hub-initiated LPM and power down their radios while they're in the
      middle of receiving a transmission.
      
      The Intel Windows folks are disabling hub-initiated LPM for all USB
      communications devices under a xHCI USB 3.0 host.  In order to keep
      the Linux behavior as close as possible to Windows, we need to do the
      same in Linux.
      
      Set the disable_hub_initiated_lpm flag for for all USB communications
      drivers.  I know there aren't currently any USB 3.0 devices that
      implement these class specifications, but we should be ready if they do.
      Signed-off-by: NSarah Sharp <sarah.a.sharp@linux.intel.com>
      Cc: Marcel Holtmann <marcel@holtmann.org>
      Cc: Gustavo Padovan <gustavo@padovan.org>
      Cc: Johan Hedberg <johan.hedberg@gmail.com>
      Cc: Hansjoerg Lipp <hjlipp@web.de>
      Cc: Tilman Schmidt <tilman@imap.cc>
      Cc: Karsten Keil <isdn@linux-pingi.de>
      Cc: Peter Korsgaard <jacmet@sunsite.dk>
      Cc: Jan Dumon <j.dumon@option.com>
      Cc: Petko Manolov <petkan@users.sourceforge.net>
      Cc: Steve Glendinning <steve.glendinning@smsc.com>
      Cc: "John W. Linville" <linville@tuxdriver.com>
      Cc: Kalle Valo <kvalo@qca.qualcomm.com>
      Cc: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>
      Cc: Jouni Malinen <jouni@qca.qualcomm.com>
      Cc: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
      Cc: Senthil Balasubramanian <senthilb@qca.qualcomm.com>
      Cc: Christian Lamparter <chunkeey@googlemail.com>
      Cc: Brett Rudley <brudley@broadcom.com>
      Cc: Roland Vossen <rvossen@broadcom.com>
      Cc: Arend van Spriel <arend@broadcom.com>
      Cc: "Franky (Zhenhui) Lin" <frankyl@broadcom.com>
      Cc: Kan Yan <kanyan@broadcom.com>
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
      Cc: Ivo van Doorn <IvDoorn@gmail.com>
      Cc: Gertjan van Wingerde <gwingerde@gmail.com>
      Cc: Helmut Schaa <helmut.schaa@googlemail.com>
      Cc: Herton Ronaldo Krzesinski <herton@canonical.com>
      Cc: Hin-Tak Leung <htl10@users.sourceforge.net>
      Cc: Larry Finger <Larry.Finger@lwfinger.net>
      Cc: Chaoming Li <chaoming_li@realsil.com.cn>
      Cc: Daniel Drake <dsd@gentoo.org>
      Cc: Ulrich Kunitz <kune@deine-taler.de>
      Signed-off-by: NSarah Sharp <sarah.a.sharp@linux.intel.com>
      e1f12eb6
  14. 17 5月, 2012 1 次提交
  15. 16 5月, 2012 2 次提交
    • N
      ath6kl: Include match ssid list in scheduled scan · dd45b759
      Naveen Singh 提交于
      Scheduled scan implementation was only taking probed list into
      consideration. The matched list was dropped. This would cause
      FW not to report the AP as the list never had that AP's SSID
      populated. This was causing long connection time when supplicant
      would just issue a wild card SSID in probed list. As a part of
      this implementation, ath6kl driver would create a complete list
      by taking both probed and matched list and pass it to FW. FW would
      probe for the SSID that it needs to and would match against the
      relevant SSIDS that is been configured.
      
      kvalo: whitespace changes, less indentation in the for loop, use ++
      Signed-off-by: NNaveen Singh <navesing@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      dd45b759
    • T
      ath6kl: enable enhanced bmiss detection · c422d52d
      Thomas Pedersen 提交于
      Enable enhanced bmiss detection if the firmware supports it. This
      feature is only enabled on some firmwares since it comes with a power
      cost.
      
      Also add a few missing command ids to keep the enums straight.
      
      kvalo: fix a compiler with ath6kl_err(), add few empty lines
      Signed-off-by: NThomas Pedersen <c_tpeder@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      c422d52d
  16. 14 5月, 2012 1 次提交
  17. 11 5月, 2012 1 次提交
  18. 05 5月, 2012 1 次提交
  19. 30 4月, 2012 2 次提交
  20. 27 4月, 2012 3 次提交
  21. 26 4月, 2012 1 次提交