1. 24 2月, 2016 1 次提交
  2. 14 1月, 2016 1 次提交
  3. 16 10月, 2015 1 次提交
  4. 08 4月, 2015 1 次提交
  5. 01 3月, 2015 1 次提交
    • J
      cfg80211-wext: export symbols only when needed · 2afe38d1
      Johannes Berg 提交于
      When a fully converted cfg80211 driver needs cfg80211-wext for
      userspace API purposes, the symbols need not be exported. When
      other drivers (orinoco/hermes or ipw2200) are enabled, they do
      need the symbols exported as they use them directly.
      
      Make those drivers select a new CFG80211_WEXT_EXPORT Kconfig
      symbol (instead of just CFG80211_WEXT) and export the functions
      only if requested - this saves about 1/2k due to the size of
      EXPORT_SYMBOL() itself.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      2afe38d1
  6. 31 12月, 2014 1 次提交
  7. 28 11月, 2014 1 次提交
    • J
      cfg80211: make WEXT compatibility unselectable · 24a0aa21
      Johannes Berg 提交于
      This option has been marked for deprecation and removal for
      a little more than two years, but it's not been very clearly
      signalled since it was always possible to just select it.
      
      Make it unselectable now to signal anyone who's still using
      it after all this time more clearly. They can still get it
      back, but only by patching the kernel.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      24a0aa21
  8. 21 7月, 2014 1 次提交
  9. 09 4月, 2014 2 次提交
    • I
      cfg80211: Enable GO operation on additional channels · 174e0cd2
      Ilan Peer 提交于
      Allow GO operation on a channel marked with IEEE80211_CHAN_GO_CONCURRENT
      iff there is an active station interface that is associated to
      an AP operating on the same channel in the 2 GHz band or the same UNII band
      (in the 5 GHz band). This relaxation is not allowed if the channel is
      marked with IEEE80211_CHAN_RADAR.
      
      Note that this is a permissive approach to the FCC definitions,
      that require a clear assessment that the device operating the AP is
      an authorized master, i.e., with radar detection and DFS capabilities.
      
      It is assumed that such restrictions are enforced by user space.
      Furthermore, it is assumed, that if the conditions that allowed for
      the operation of the GO on such a channel change, i.e., the station
      interface disconnected from the AP, it is the responsibility of user
      space to evacuate the GO from the channel.
      Signed-off-by: NIlan Peer <ilan.peer@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      174e0cd2
    • I
      cfg80211: Add Kconfig option for cellular BS hints · 94fc661f
      Ilan Peer 提交于
      Move the regulatory cellular base station hints support under
      a specific configuration option and make the option depend
      on CFG80211_CERTIFICATION_ONUS.
      Signed-off-by: NIlan Peer <ilan.peer@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      94fc661f
  10. 17 11月, 2012 1 次提交
  11. 17 7月, 2012 1 次提交
    • L
      cfg80211: add CONFIG_CFG80211_CERTIFICATION_ONUS · b594bab9
      Luis R. Rodriguez 提交于
      This adds CONFIG_CFG80211_CERTIFICATION_ONUS which is to
      be used for features / code which require a bit of work on
      the system integrator's part to ensure that the system will
      still pass 802.11 regulatory certification. This option is
      also usable for researchers and experimenters looking to add
      code in the kernel without impacting compliant code.
      
      We'd use CONFIG_EXPERT alone but it seems that most standard
      Linux distributions are enabling CONFIG_EXPERT already. This
      allows us to define 802.11 specific kernel features under a
      flag that is intended by design to be disabled by standard
      Linux distributions, and only enabled by system integrators
      or distributions that have done work to ensure regulatory
      certification on the system with the enabled features.
      Signed-off-by: NLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      b594bab9
  12. 06 6月, 2012 2 次提交
  13. 08 12月, 2011 1 次提交
  14. 21 1月, 2011 1 次提交
    • D
      kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT · 6a108a14
      David Rientjes 提交于
      The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
      is used to configure any non-standard kernel with a much larger scope than
      only small devices.
      
      This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
      references to the option throughout the kernel.  A new CONFIG_EMBEDDED
      option is added that automatically selects CONFIG_EXPERT when enabled and
      can be used in the future to isolate options that should only be
      considered for embedded systems (RISC architectures, SLOB, etc).
      
      Calling the option "EXPERT" more accurately represents its intention: only
      expert users who understand the impact of the configuration changes they
      are making should enable it.
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NDavid Woodhouse <david.woodhouse@intel.com>
      Signed-off-by: NDavid Rientjes <rientjes@google.com>
      Cc: Greg KH <gregkh@suse.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Robin Holt <holt@sgi.com>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6a108a14
  15. 29 12月, 2009 1 次提交
  16. 22 12月, 2009 1 次提交
  17. 20 11月, 2009 1 次提交
  18. 08 10月, 2009 1 次提交
    • J
      wext: refactor · 3d23e349
      Johannes Berg 提交于
      Refactor wext to
       * split out iwpriv handling
       * split out iwspy handling
       * split out procfs support
       * allow cfg80211 to have wireless extensions compat code
         w/o CONFIG_WIRELESS_EXT
      
      After this, drivers need to
       - select WIRELESS_EXT	- for wext support
       - select WEXT_PRIV	- for iwpriv support
       - select WEXT_SPY	- for iwspy support
      
      except cfg80211 -- which gets new hooks in wext-core.c
      and can then get wext handlers without CONFIG_WIRELESS_EXT.
      
      Wireless extensions procfs support is auto-selected
      based on PROC_FS and anything that requires the wext core
      (i.e. WIRELESS_EXT or CFG80211_WEXT).
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3d23e349
  19. 09 9月, 2009 1 次提交
  20. 03 9月, 2009 1 次提交
  21. 29 8月, 2009 1 次提交
    • J
      cfg80211: make spurious warnings less likely, configurable · f7969969
      Johannes Berg 提交于
      Bob reported that he got warnings in IBSS mode about
      the ssid_len being zero on a joined event, but only
      when kmemcheck was enabled. This appears to be due
      to a race condition between drivers and userspace,
      when the driver reports joined but the user in the
      meantime decided to leave the IBSS again, the warning
      would trigger. This was made more likely by kmemcheck
      delaying the code that does the check and sends the
      event.
      
      So first, make the warning trigger closer to the
      driver, which means it's not locked, but since only
      the warning depends on it that's ok.
      
      And secondly, users will not want to have spurious
      warnings at all, so make those that are known to be
      racy in such a way configurable.
      Reported-by: NBob Copeland <me@bobcopeland.com>
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f7969969
  22. 11 7月, 2009 3 次提交
    • J
      cfg80211: implement iwpower · bc92afd9
      Johannes Berg 提交于
      Just on/off and timeout, and with a hacky cfg80211 method
      until we figure out what we want, though this is probably
      sufficient as we want to use pm_qos for wifi everywhere.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      bc92afd9
    • J
      cfg80211: introduce nl80211 testmode command · aff89a9b
      Johannes Berg 提交于
      This introduces a new NL80211_CMD_TESTMODE for testing
      and calibration use with nl80211. There's no multiplexing
      like like iwpriv had, and the command is not available by
      default, it needs to be explicitly enabled in Kconfig and
      shouldn't be enabled in most kernels.
      
      The command requires a wiphy index or interface index to
      identify the device to operate on, and the new TESTDATA
      attribute. There also is API for sending replies to the
      command, and testmode multicast messages (on a testmode
      multicast group).
      
      I've also updated mac80211 to be able to pass through the
      command to the driver, since it itself doesn't implement
      the testmode command.
      
      Additionally, to give people an idea of how to use the
      command, I've added a little code to hwsim that makes use
      of the new command to set the powersave mode, this is
      currently done via debugfs and should remain there, and
      the testmode command only serves as an example of how to
      use this best -- with nested netlink attributes in the
      TESTDATA attribute. A hwsim testmode tool can be found at
      http://git.sipsolutions.net/hwsim.git/. This tool is BSD
      licensed so people can easily use it as a basis for their
      own internal fabrication and validation tools.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      aff89a9b
    • J
      wext: default to y · 89832402
      Johannes Berg 提交于
      The way I initially thought we could do wireless extensions
      is by making all the compat code in cfg80211 be independent
      of CONFIG_WIRELESS_EXT, but this is turning out to not be
      feasible. Therefore, fix the Kconfig help text and make the
      option default to yes, so people won't get a nasty surprise
      when mac80211 will get rid of its 'select WIRELESS_EXT' any
      time now.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      89832402
  23. 04 6月, 2009 1 次提交
  24. 21 5月, 2009 1 次提交
  25. 28 3月, 2009 2 次提交
  26. 17 3月, 2009 1 次提交
  27. 26 11月, 2008 1 次提交
    • L
      cfg80211/mac80211: Add 802.11d support · 3f2355cb
      Luis R. Rodriguez 提交于
      This adds country IE parsing to mac80211 and enables its usage
      within the new regulatory infrastructure in cfg80211. We parse
      the country IEs only on management beacons for the BSSID you are
      associated to and disregard the IEs when the country and environment
      (indoor, outdoor, any) matches the already processed country IE.
      
      To avoid following misinformed or outdated APs we build and use
      a regulatory domain out of the intersection between what the AP
      provides us on the country IE and what CRDA is aware is allowed
      on the same country.
      
      A secondary device is allowed to follow only the same country IE
      as it make no sense for two devices on a system to be in two
      different countries.
      
      In the case the AP is using country IEs for an incorrect country
      the user may help compliance further by setting the regulatory
      domain before or after the IE is parsed and in that case another
      intersection will be performed.
      
      CONFIG_WIRELESS_OLD_REGULATORY is supported but requires CRDA
      present.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Acked-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3f2355cb
  28. 22 11月, 2008 1 次提交
  29. 01 11月, 2008 1 次提交
  30. 27 10月, 2008 1 次提交
  31. 07 10月, 2008 1 次提交
  32. 16 9月, 2008 1 次提交
    • L
      cfg80211: Add new wireless regulatory infrastructure · b2e1b302
      Luis R. Rodriguez 提交于
      This adds the new wireless regulatory infrastructure. The
      main motiviation behind this was to centralize regulatory
      code as each driver was implementing their own regulatory solution,
      and to replace the initial centralized code we have where:
      
      * only 3 regulatory domains are supported: US, JP and EU
      * regulatory domains can only be changed through module parameter
      * all rules were built statically in the kernel
      
      We now have support for regulatory domains for many countries
      and regulatory domains are now queried through a userspace agent
      through udev allowing distributions to update regulatory rules
      without updating the kernel.
      
      Each driver can regulatory_hint() a regulatory domain
      based on either their EEPROM mapped regulatory domain value to a
      respective ISO/IEC 3166-1 country code or pass an internally built
      regulatory domain. We also add support to let the user set the
      regulatory domain through userspace in case of faulty EEPROMs to
      further help compliance.
      
      Support for world roaming will be added soon for cards capable of
      this.
      
      For more information see:
      
      http://wireless.kernel.org/en/developers/Regulatory/CRDA
      
      For now we leave an option to enable the old module parameter,
      ieee80211_regdom, and to build the 3 old regdomains statically
      (US, JP and EU). This option is CONFIG_WIRELESS_OLD_REGULATORY.
      These old static definitions and the module parameter is being
      scheduled for removal for 2.6.29. Note that if you use this
      you won't make use of a world regulatory domain as its pointless.
      If you leave this option enabled and if CRDA is present and you
      use US or JP we will try to ask CRDA to update us a regulatory
      domain for us.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b2e1b302
  33. 03 9月, 2008 1 次提交
  34. 15 7月, 2008 1 次提交
  35. 29 1月, 2008 1 次提交