Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. config CFG80211
  2. tristate "Improved wireless configuration API"
  3. config CFG80211_REG_DEBUG
  4. bool "cfg80211 regulatory debugging"
  5. depends on CFG80211
  6. default n
  7. ---help---
  8. You can enable this if you want to debug regulatory changes.
  9. If unsure, say N.
  10. config NL80211
  11. bool "nl80211 new netlink interface support"
  12. depends on CFG80211
  13. default y
  14. ---help---
  15. This option turns on the new netlink interface
  16. (nl80211) support in cfg80211.
  17. If =n, drivers using mac80211 will be configured via
  18. wireless extension support provided by that subsystem.
  19. If unsure, say Y.
  20. config WIRELESS_OLD_REGULATORY
  21. bool "Old wireless static regulatory definitions"
  22. default y
  23. ---help---
  24. This option enables the old static regulatory information
  25. and uses it within the new framework. This is available
  26. temporarily as an option to help prevent immediate issues
  27. due to the switch to the new regulatory framework which
  28. does require a new userspace application which has the
  29. database of regulatory information (CRDA) and another for
  30. setting regulatory domains (iw).
  31. For more information see:
  32. http://wireless.kernel.org/en/developers/Regulatory/CRDA
  33. http://wireless.kernel.org/en/users/Documentation/iw
  34. It is important to note though that if you *do* have CRDA present
  35. and if this option is enabled CRDA *will* be called to update the
  36. regulatory domain (for US and JP only). Support for letting the user
  37. set the regulatory domain through iw is also supported. This option
  38. mainly exists to leave around for a kernel release some old static
  39. regulatory domains that were defined and to keep around the old
  40. ieee80211_regdom module parameter. This is being phased out and you
  41. should stop using them ASAP.
  42. Note: You will need CRDA if you want 802.11d support
  43. Say Y unless you have installed a new userspace application.
  44. Also say Y if have one currently depending on the ieee80211_regdom
  45. module parameter and cannot port it to use the new userspace
  46. interfaces.
  47. config WIRELESS_EXT
  48. bool "Wireless extensions"
  49. default n
  50. ---help---
  51. This option enables the legacy wireless extensions
  52. (wireless network interface configuration via ioctls.)
  53. Wireless extensions will be replaced by cfg80211 and
  54. will be required only by legacy drivers that implement
  55. wireless extension handlers. This option does not
  56. affect the wireless-extension backward compatibility
  57. code in cfg80211.
  58. Say N (if you can) unless you know you need wireless
  59. extensions for external modules.
  60. config WIRELESS_EXT_SYSFS
  61. bool "Wireless extensions sysfs files"
  62. default y
  63. depends on WIRELESS_EXT && SYSFS
  64. help
  65. This option enables the deprecated wireless statistics
  66. files in /sys/class/net/*/wireless/. The same information
  67. is available via the ioctls as well.
  68. Say Y if you have programs using it, like old versions of
  69. hal.
  70. config LIB80211
  71. tristate "Common routines for IEEE802.11 drivers"
  72. default n
  73. help
  74. This options enables a library of common routines used
  75. by IEEE802.11 wireless LAN drivers.
  76. Drivers should select this themselves if needed. Say Y if
  77. you want this built into your kernel.
  78. config LIB80211_CRYPT_WEP
  79. tristate
  80. config LIB80211_CRYPT_CCMP
  81. tristate
  82. config LIB80211_CRYPT_TKIP
  83. tristate