forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2024-02-19 1c055e55a242a33e574e48be530e06770a210dcd 
 kernel/drivers/net/wireless/intel/ipw2x00/Kconfig
....@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
12 #
23 # Intel Centrino wireless drivers
34 #
....@@ -11,56 +12,56 @@
1112 	select FW_LOADER
1213 	select LIB80211
1314 	select LIBIPW
14
-	---help---
15
-          A driver for the Intel PRO/Wireless 2100 Network 
15
+	help
16
+	  A driver for the Intel PRO/Wireless 2100 Network
1617 	  Connection 802.11b wireless network adapter.
1718 
18
-          See <file:Documentation/networking/README.ipw2100> for information on
19
-          the capabilities currently enabled in this driver and for tips
20
-          for debugging issues and problems.
19
+	  See <file:Documentation/networking/device_drivers/wifi/intel/ipw2100.rst>
20
+	  for information on the capabilities currently enabled in this driver
21
+	  and for tips for debugging issues and problems.
2122 
2223 	  In order to use this driver, you will need a firmware image for it.
23
-          You can obtain the firmware from
24
-	  <http://ipw2100.sf.net/>.  Once you have the firmware image, you 
24
+	  You can obtain the firmware from
25
+	  <http://ipw2100.sf.net/>.  Once you have the firmware image, you
2526 	  will need to place it in /lib/firmware.
2627 
27
-          You will also very likely need the Wireless Tools in order to
28
-          configure your card:
28
+	  You will also very likely need the Wireless Tools in order to
29
+	  configure your card:
2930 
30
-          <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
31
+	  <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
3132 
32
-          It is recommended that you compile this driver as a module (M)
33
-          rather than built-in (Y). This driver requires firmware at device
34
-          initialization time, and when built-in this typically happens
35
-          before the filesystem is accessible (hence firmware will be
36
-          unavailable and initialization will fail). If you do choose to build
37
-          this driver into your kernel image, you can avoid this problem by
38
-          including the firmware and a firmware loader in an initramfs.
39
- 
33
+	  It is recommended that you compile this driver as a module (M)
34
+	  rather than built-in (Y). This driver requires firmware at device
35
+	  initialization time, and when built-in this typically happens
36
+	  before the filesystem is accessible (hence firmware will be
37
+	  unavailable and initialization will fail). If you do choose to build
38
+	  this driver into your kernel image, you can avoid this problem by
39
+	  including the firmware and a firmware loader in an initramfs.
40
+
4041 config IPW2100_MONITOR
41
-        bool "Enable promiscuous mode"
42
-        depends on IPW2100
43
-        ---help---
42
+	bool "Enable promiscuous mode"
43
+	depends on IPW2100
44
+	help
4445 	  Enables promiscuous/monitor mode support for the ipw2100 driver.
45
-	  With this feature compiled into the driver, you can switch to 
46
+	  With this feature compiled into the driver, you can switch to
4647 	  promiscuous mode via the Wireless Tool's Monitor mode.  While in this
4748 	  mode, no packets can be sent.
4849 
4950 config IPW2100_DEBUG
5051 	bool "Enable full debugging output in IPW2100 module."
5152 	depends on IPW2100
52
-	---help---
53
-	  This option will enable debug tracing output for the IPW2100.  
53
+	help
54
+	  This option will enable debug tracing output for the IPW2100.
5455 
55
-	  This will result in the kernel module being ~60k larger.  You can 
56
-	  control which debug output is sent to the kernel log by setting the 
57
-	  value in 
56
+	  This will result in the kernel module being ~60k larger.  You can
57
+	  control which debug output is sent to the kernel log by setting the
58
+	  value in
5859 
5960 	  /sys/bus/pci/drivers/ipw2100/debug_level
6061 
6162 	  This entry will only exist if this option is enabled.
6263 
63
-	  If you are not trying to debug or develop the IPW2100 driver, you 
64
+	  If you are not trying to debug or develop the IPW2100 driver, you
6465 	  most likely want to say N here.
6566 
6667 config IPW2200
....@@ -73,38 +74,38 @@
7374 	select FW_LOADER
7475 	select LIB80211
7576 	select LIBIPW
76
-	---help---
77
-          A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network
78
-	  Connection adapters. 
77
+	help
78
+	  A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network
79
+	  Connection adapters.
7980 
80
-          See <file:Documentation/networking/README.ipw2200> for 
81
-	  information on the capabilities currently enabled in this 
81
+	  See <file:Documentation/networking/device_drivers/wifi/intel/ipw2200.rst>
82
+	  for information on the capabilities currently enabled in this
8283 	  driver and for tips for debugging issues and problems.
8384 
8485 	  In order to use this driver, you will need a firmware image for it.
85
-          You can obtain the firmware from
86
-	  <http://ipw2200.sf.net/>.  See the above referenced README.ipw2200 
86
+	  You can obtain the firmware from
87
+	  <http://ipw2200.sf.net/>.  See the above referenced README.ipw2200
8788 	  for information on where to install the firmware images.
8889 
89
-          You will also very likely need the Wireless Tools in order to
90
-          configure your card:
90
+	  You will also very likely need the Wireless Tools in order to
91
+	  configure your card:
9192 
92
-          <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
93
+	  <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
9394 
94
-          It is recommended that you compile this driver as a module (M)
95
-          rather than built-in (Y). This driver requires firmware at device
96
-          initialization time, and when built-in this typically happens
97
-          before the filesystem is accessible (hence firmware will be
98
-          unavailable and initialization will fail). If you do choose to build
99
-          this driver into your kernel image, you can avoid this problem by
100
-          including the firmware and a firmware loader in an initramfs.
95
+	  It is recommended that you compile this driver as a module (M)
96
+	  rather than built-in (Y). This driver requires firmware at device
97
+	  initialization time, and when built-in this typically happens
98
+	  before the filesystem is accessible (hence firmware will be
99
+	  unavailable and initialization will fail). If you do choose to build
100
+	  this driver into your kernel image, you can avoid this problem by
101
+	  including the firmware and a firmware loader in an initramfs.
101102 
102103 config IPW2200_MONITOR
103
-        bool "Enable promiscuous mode"
104
-        depends on IPW2200
105
-        ---help---
104
+	bool "Enable promiscuous mode"
105
+	depends on IPW2200
106
+	help
106107 	  Enables promiscuous/monitor mode support for the ipw2200 driver.
107
-	  With this feature compiled into the driver, you can switch to 
108
+	  With this feature compiled into the driver, you can switch to
108109 	  promiscuous mode via the Wireless Tool's Monitor mode.  While in this
109110 	  mode, no packets can be sent.
110111 
....@@ -116,34 +117,34 @@
116117 	bool "Enable creation of a RF radiotap promiscuous interface"
117118 	depends on IPW2200_MONITOR
118119 	select IPW2200_RADIOTAP
119
-	---help---
120
-          Enables the creation of a second interface prefixed 'rtap'. 
121
-          This second interface will provide every received in radiotap
120
+	help
121
+	  Enables the creation of a second interface prefixed 'rtap'.
122
+	  This second interface will provide every received in radiotap
122123 	  format.
123124 
124
-          This is useful for performing wireless network analysis while
125
-          maintaining an active association.
125
+	  This is useful for performing wireless network analysis while
126
+	  maintaining an active association.
126127 
127
-          Example usage:
128
+	  Example usage:
128129 
129
-            % modprobe ipw2200 rtap_iface=1
130
-            % ifconfig rtap0 up
131
-            % tethereal -i rtap0
130
+	    % modprobe ipw2200 rtap_iface=1
131
+	    % ifconfig rtap0 up
132
+	    % tethereal -i rtap0
132133 
133
-          If you do not specify 'rtap_iface=1' as a module parameter then 
134
-          the rtap interface will not be created and you will need to turn 
135
-          it on via sysfs:
136
-	
137
-            % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
134
+	  If you do not specify 'rtap_iface=1' as a module parameter then
135
+	  the rtap interface will not be created and you will need to turn
136
+	  it on via sysfs:
137
+
138
+	    % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
138139 
139140 config IPW2200_QOS
140
-        bool "Enable QoS support"
141
-        depends on IPW2200
141
+	bool "Enable QoS support"
142
+	depends on IPW2200
142143 
143144 config IPW2200_DEBUG
144145 	bool "Enable full debugging output in IPW2200 module."
145146 	depends on IPW2200
146
-	---help---
147
+	help
147148 	  This option will enable low level debug tracing output for IPW2200.
148149 
149150 	  Note, normal debug code is already compiled in. This low level
....@@ -159,17 +160,13 @@
159160 	select WIRELESS_EXT
160161 	select WEXT_SPY
161162 	select CRYPTO
162
-	select CRYPTO_ARC4
163
-	select CRYPTO_ECB
164
-	select CRYPTO_AES
165163 	select CRYPTO_MICHAEL_MIC
166
-	select CRYPTO_ECB
167164 	select CRC32
168165 	select LIB80211
169166 	select LIB80211_CRYPT_WEP
170167 	select LIB80211_CRYPT_TKIP
171168 	select LIB80211_CRYPT_CCMP
172
-	---help---
169
+	help
173170 	This option enables the hardware independent IEEE 802.11
174171 	networking stack.  This component is deprecated in favor of the
175172 	mac80211 component.
....@@ -177,7 +174,7 @@
177174 config LIBIPW_DEBUG
178175 	bool "Full debugging output for the LIBIPW component"
179176 	depends on LIBIPW
180
-	---help---
177
+	help
181178 	  This option will enable debug tracing output for the
182179 	  libipw component.
183180