diff options
-rw-r--r-- | Documentation/networking/README.ipw2100 | 132 | ||||
-rw-r--r-- | Documentation/networking/README.ipw2200 | 196 | ||||
-rw-r--r-- | MAINTAINERS | 18 |
3 files changed, 272 insertions, 74 deletions
diff --git a/Documentation/networking/README.ipw2100 b/Documentation/networking/README.ipw2100 index 2046948b020d..3ab40379d1cf 100644 --- a/Documentation/networking/README.ipw2100 +++ b/Documentation/networking/README.ipw2100 | |||
@@ -1,27 +1,82 @@ | |||
1 | 1 | ||
2 | =========================== | 2 | Intel(R) PRO/Wireless 2100 Driver for Linux in support of: |
3 | Intel(R) PRO/Wireless 2100 Network Connection Driver for Linux | 3 | |
4 | Intel(R) PRO/Wireless 2100 Network Connection | ||
5 | |||
6 | Copyright (C) 2003-2005, Intel Corporation | ||
7 | |||
4 | README.ipw2100 | 8 | README.ipw2100 |
5 | 9 | ||
6 | March 14, 2005 | 10 | Version: 1.1.3 |
11 | Date : October 17, 2005 | ||
7 | 12 | ||
8 | =========================== | ||
9 | Index | 13 | Index |
10 | --------------------------- | 14 | ----------------------------------------------- |
11 | 0. Introduction | 15 | 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER |
12 | 1. Release 1.1.0 Current Features | 16 | 1. Introduction |
13 | 2. Command Line Parameters | 17 | 2. Release 1.1.3 Current Features |
14 | 3. Sysfs Helper Files | 18 | 3. Command Line Parameters |
15 | 4. Radio Kill Switch | 19 | 4. Sysfs Helper Files |
16 | 5. Dynamic Firmware | 20 | 5. Radio Kill Switch |
17 | 6. Power Management | 21 | 6. Dynamic Firmware |
18 | 7. Support | 22 | 7. Power Management |
19 | 8. License | 23 | 8. Support |
20 | 24 | 9. License | |
21 | 25 | ||
22 | =========================== | 26 | |
23 | 0. Introduction | 27 | 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER |
24 | ------------ ----- ----- ---- --- -- - | 28 | ----------------------------------------------- |
29 | |||
30 | Important Notice FOR ALL USERS OR DISTRIBUTORS!!!! | ||
31 | |||
32 | Intel wireless LAN adapters are engineered, manufactured, tested, and | ||
33 | quality checked to ensure that they meet all necessary local and | ||
34 | governmental regulatory agency requirements for the regions that they | ||
35 | are designated and/or marked to ship into. Since wireless LANs are | ||
36 | generally unlicensed devices that share spectrum with radars, | ||
37 | satellites, and other licensed and unlicensed devices, it is sometimes | ||
38 | necessary to dynamically detect, avoid, and limit usage to avoid | ||
39 | interference with these devices. In many instances Intel is required to | ||
40 | provide test data to prove regional and local compliance to regional and | ||
41 | governmental regulations before certification or approval to use the | ||
42 | product is granted. Intel's wireless LAN's EEPROM, firmware, and | ||
43 | software driver are designed to carefully control parameters that affect | ||
44 | radio operation and to ensure electromagnetic compliance (EMC). These | ||
45 | parameters include, without limitation, RF power, spectrum usage, | ||
46 | channel scanning, and human exposure. | ||
47 | |||
48 | For these reasons Intel cannot permit any manipulation by third parties | ||
49 | of the software provided in binary format with the wireless WLAN | ||
50 | adapters (e.g., the EEPROM and firmware). Furthermore, if you use any | ||
51 | patches, utilities, or code with the Intel wireless LAN adapters that | ||
52 | have been manipulated by an unauthorized party (i.e., patches, | ||
53 | utilities, or code (including open source code modifications) which have | ||
54 | not been validated by Intel), (i) you will be solely responsible for | ||
55 | ensuring the regulatory compliance of the products, (ii) Intel will bear | ||
56 | no liability, under any theory of liability for any issues associated | ||
57 | with the modified products, including without limitation, claims under | ||
58 | the warranty and/or issues arising from regulatory non-compliance, and | ||
59 | (iii) Intel will not provide or be required to assist in providing | ||
60 | support to any third parties for such modified products. | ||
61 | |||
62 | Note: Many regulatory agencies consider Wireless LAN adapters to be | ||
63 | modules, and accordingly, condition system-level regulatory approval | ||
64 | upon receipt and review of test data documenting that the antennas and | ||
65 | system configuration do not cause the EMC and radio operation to be | ||
66 | non-compliant. | ||
67 | |||
68 | The drivers available for download from SourceForge are provided as a | ||
69 | part of a development project. Conformance to local regulatory | ||
70 | requirements is the responsibility of the individual developer. As | ||
71 | such, if you are interested in deploying or shipping a driver as part of | ||
72 | solution intended to be used for purposes other than development, please | ||
73 | obtain a tested driver from Intel Customer Support at: | ||
74 | |||
75 | http://support.intel.com/support/notebook/sb/CS-006408.htm | ||
76 | |||
77 | |||
78 | 1. Introduction | ||
79 | ----------------------------------------------- | ||
25 | 80 | ||
26 | This document provides a brief overview of the features supported by the | 81 | This document provides a brief overview of the features supported by the |
27 | IPW2100 driver project. The main project website, where the latest | 82 | IPW2100 driver project. The main project website, where the latest |
@@ -34,9 +89,8 @@ potential fixes and patches, as well as links to the development mailing list | |||
34 | for the driver project. | 89 | for the driver project. |
35 | 90 | ||
36 | 91 | ||
37 | =========================== | 92 | 2. Release 1.1.3 Current Supported Features |
38 | 1. Release 1.1.0 Current Supported Features | 93 | ----------------------------------------------- |
39 | --------------------------- | ||
40 | - Managed (BSS) and Ad-Hoc (IBSS) | 94 | - Managed (BSS) and Ad-Hoc (IBSS) |
41 | - WEP (shared key and open) | 95 | - WEP (shared key and open) |
42 | - Wireless Tools support | 96 | - Wireless Tools support |
@@ -51,9 +105,8 @@ on the amount of validation and interoperability testing that has been | |||
51 | performed on a given feature. | 105 | performed on a given feature. |
52 | 106 | ||
53 | 107 | ||
54 | =========================== | 108 | 3. Command Line Parameters |
55 | 2. Command Line Parameters | 109 | ----------------------------------------------- |
56 | --------------------------- | ||
57 | 110 | ||
58 | If the driver is built as a module, the following optional parameters are used | 111 | If the driver is built as a module, the following optional parameters are used |
59 | by entering them on the command line with the modprobe command using this | 112 | by entering them on the command line with the modprobe command using this |
@@ -75,9 +128,9 @@ associate boolean associate=0 /* Do NOT auto associate */ | |||
75 | disable boolean disable=1 /* Do not power the HW */ | 128 | disable boolean disable=1 /* Do not power the HW */ |
76 | 129 | ||
77 | 130 | ||
78 | =========================== | 131 | 4. Sysfs Helper Files |
79 | 3. Sysfs Helper Files | ||
80 | --------------------------- | 132 | --------------------------- |
133 | ----------------------------------------------- | ||
81 | 134 | ||
82 | There are several ways to control the behavior of the driver. Many of the | 135 | There are several ways to control the behavior of the driver. Many of the |
83 | general capabilities are exposed through the Wireless Tools (iwconfig). There | 136 | general capabilities are exposed through the Wireless Tools (iwconfig). There |
@@ -120,9 +173,8 @@ For the device level files, see /sys/bus/pci/drivers/ipw2100: | |||
120 | based RF kill from ON -> OFF -> ON, the radio will NOT come back on | 173 | based RF kill from ON -> OFF -> ON, the radio will NOT come back on |
121 | 174 | ||
122 | 175 | ||
123 | =========================== | 176 | 5. Radio Kill Switch |
124 | 4. Radio Kill Switch | 177 | ----------------------------------------------- |
125 | --------------------------- | ||
126 | Most laptops provide the ability for the user to physically disable the radio. | 178 | Most laptops provide the ability for the user to physically disable the radio. |
127 | Some vendors have implemented this as a physical switch that requires no | 179 | Some vendors have implemented this as a physical switch that requires no |
128 | software to turn the radio off and on. On other laptops, however, the switch | 180 | software to turn the radio off and on. On other laptops, however, the switch |
@@ -134,9 +186,8 @@ See the Sysfs helper file 'rf_kill' for determining the state of the RF switch | |||
134 | on your system. | 186 | on your system. |
135 | 187 | ||
136 | 188 | ||
137 | =========================== | 189 | 6. Dynamic Firmware |
138 | 5. Dynamic Firmware | 190 | ----------------------------------------------- |
139 | --------------------------- | ||
140 | As the firmware is licensed under a restricted use license, it can not be | 191 | As the firmware is licensed under a restricted use license, it can not be |
141 | included within the kernel sources. To enable the IPW2100 you will need a | 192 | included within the kernel sources. To enable the IPW2100 you will need a |
142 | firmware image to load into the wireless NIC's processors. | 193 | firmware image to load into the wireless NIC's processors. |
@@ -146,9 +197,8 @@ You can obtain these images from <http://ipw2100.sf.net/firmware.php>. | |||
146 | See INSTALL for instructions on installing the firmware. | 197 | See INSTALL for instructions on installing the firmware. |
147 | 198 | ||
148 | 199 | ||
149 | =========================== | 200 | 7. Power Management |
150 | 6. Power Management | 201 | ----------------------------------------------- |
151 | --------------------------- | ||
152 | The IPW2100 supports the configuration of the Power Save Protocol | 202 | The IPW2100 supports the configuration of the Power Save Protocol |
153 | through a private wireless extension interface. The IPW2100 supports | 203 | through a private wireless extension interface. The IPW2100 supports |
154 | the following different modes: | 204 | the following different modes: |
@@ -200,9 +250,8 @@ xxxx/yyyy will be replaced with 'off' -- the level reported will be the active | |||
200 | level if `iwconfig eth1 power on` is invoked. | 250 | level if `iwconfig eth1 power on` is invoked. |
201 | 251 | ||
202 | 252 | ||
203 | =========================== | 253 | 8. Support |
204 | 7. Support | 254 | ----------------------------------------------- |
205 | --------------------------- | ||
206 | 255 | ||
207 | For general development information and support, | 256 | For general development information and support, |
208 | go to: | 257 | go to: |
@@ -218,9 +267,8 @@ For installation support on the ipw2100 1.1.0 driver on Linux kernels | |||
218 | 267 | ||
219 | http://supportmail.intel.com | 268 | http://supportmail.intel.com |
220 | 269 | ||
221 | =========================== | 270 | 9. License |
222 | 8. License | 271 | ----------------------------------------------- |
223 | --------------------------- | ||
224 | 272 | ||
225 | Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved. | 273 | Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved. |
226 | 274 | ||
diff --git a/Documentation/networking/README.ipw2200 b/Documentation/networking/README.ipw2200 index 6916080c5f03..c6492d3839fa 100644 --- a/Documentation/networking/README.ipw2200 +++ b/Documentation/networking/README.ipw2200 | |||
@@ -1,33 +1,89 @@ | |||
1 | 1 | ||
2 | Intel(R) PRO/Wireless 2915ABG Driver for Linux in support of: | 2 | Intel(R) PRO/Wireless 2915ABG Driver for Linux in support of: |
3 | 3 | ||
4 | Intel(R) PRO/Wireless 2200BG Network Connection | 4 | Intel(R) PRO/Wireless 2200BG Network Connection |
5 | Intel(R) PRO/Wireless 2915ABG Network Connection | 5 | Intel(R) PRO/Wireless 2915ABG Network Connection |
6 | 6 | ||
7 | Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R) | 7 | Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R) |
8 | PRO/Wireless 2200BG Driver for Linux is a unified driver that works on | 8 | PRO/Wireless 2200BG Driver for Linux is a unified driver that works on |
9 | both hardware adapters listed above. In this document the Intel(R) | 9 | both hardware adapters listed above. In this document the Intel(R) |
10 | PRO/Wireless 2915ABG Driver for Linux will be used to reference the | 10 | PRO/Wireless 2915ABG Driver for Linux will be used to reference the |
11 | unified driver. | 11 | unified driver. |
12 | 12 | ||
13 | Copyright (C) 2004-2005, Intel Corporation | 13 | Copyright (C) 2004-2005, Intel Corporation |
14 | 14 | ||
15 | README.ipw2200 | 15 | README.ipw2200 |
16 | 16 | ||
17 | Version: 1.0.0 | 17 | Version: 1.0.8 |
18 | Date : January 31, 2005 | 18 | Date : October 20, 2005 |
19 | 19 | ||
20 | 20 | ||
21 | Index | 21 | Index |
22 | ----------------------------------------------- | 22 | ----------------------------------------------- |
23 | 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER | ||
23 | 1. Introduction | 24 | 1. Introduction |
24 | 1.1. Overview of features | 25 | 1.1. Overview of features |
25 | 1.2. Module parameters | 26 | 1.2. Module parameters |
26 | 1.3. Wireless Extension Private Methods | 27 | 1.3. Wireless Extension Private Methods |
27 | 1.4. Sysfs Helper Files | 28 | 1.4. Sysfs Helper Files |
28 | 2. About the Version Numbers | 29 | 2. Ad-Hoc Networking |
29 | 3. Support | 30 | 3. Interacting with Wireless Tools |
30 | 4. License | 31 | 3.1. iwconfig mode |
32 | 4. About the Version Numbers | ||
33 | 5. Firmware installation | ||
34 | 6. Support | ||
35 | 7. License | ||
36 | |||
37 | |||
38 | 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER | ||
39 | ----------------------------------------------- | ||
40 | |||
41 | Important Notice FOR ALL USERS OR DISTRIBUTORS!!!! | ||
42 | |||
43 | Intel wireless LAN adapters are engineered, manufactured, tested, and | ||
44 | quality checked to ensure that they meet all necessary local and | ||
45 | governmental regulatory agency requirements for the regions that they | ||
46 | are designated and/or marked to ship into. Since wireless LANs are | ||
47 | generally unlicensed devices that share spectrum with radars, | ||
48 | satellites, and other licensed and unlicensed devices, it is sometimes | ||
49 | necessary to dynamically detect, avoid, and limit usage to avoid | ||
50 | interference with these devices. In many instances Intel is required to | ||
51 | provide test data to prove regional and local compliance to regional and | ||
52 | governmental regulations before certification or approval to use the | ||
53 | product is granted. Intel's wireless LAN's EEPROM, firmware, and | ||
54 | software driver are designed to carefully control parameters that affect | ||
55 | radio operation and to ensure electromagnetic compliance (EMC). These | ||
56 | parameters include, without limitation, RF power, spectrum usage, | ||
57 | channel scanning, and human exposure. | ||
58 | |||
59 | For these reasons Intel cannot permit any manipulation by third parties | ||
60 | of the software provided in binary format with the wireless WLAN | ||
61 | adapters (e.g., the EEPROM and firmware). Furthermore, if you use any | ||
62 | patches, utilities, or code with the Intel wireless LAN adapters that | ||
63 | have been manipulated by an unauthorized party (i.e., patches, | ||
64 | utilities, or code (including open source code modifications) which have | ||
65 | not been validated by Intel), (i) you will be solely responsible for | ||
66 | ensuring the regulatory compliance of the products, (ii) Intel will bear | ||
67 | no liability, under any theory of liability for any issues associated | ||
68 | with the modified products, including without limitation, claims under | ||
69 | the warranty and/or issues arising from regulatory non-compliance, and | ||
70 | (iii) Intel will not provide or be required to assist in providing | ||
71 | support to any third parties for such modified products. | ||
72 | |||
73 | Note: Many regulatory agencies consider Wireless LAN adapters to be | ||
74 | modules, and accordingly, condition system-level regulatory approval | ||
75 | upon receipt and review of test data documenting that the antennas and | ||
76 | system configuration do not cause the EMC and radio operation to be | ||
77 | non-compliant. | ||
78 | |||
79 | The drivers available for download from SourceForge are provided as a | ||
80 | part of a development project. Conformance to local regulatory | ||
81 | requirements is the responsibility of the individual developer. As | ||
82 | such, if you are interested in deploying or shipping a driver as part of | ||
83 | solution intended to be used for purposes other than development, please | ||
84 | obtain a tested driver from Intel Customer Support at: | ||
85 | |||
86 | http://support.intel.com/support/notebook/sb/CS-006408.htm | ||
31 | 87 | ||
32 | 88 | ||
33 | 1. Introduction | 89 | 1. Introduction |
@@ -45,7 +101,7 @@ file. | |||
45 | 101 | ||
46 | 1.1. Overview of Features | 102 | 1.1. Overview of Features |
47 | ----------------------------------------------- | 103 | ----------------------------------------------- |
48 | The current release (1.0.0) supports the following features: | 104 | The current release (1.0.8) supports the following features: |
49 | 105 | ||
50 | + BSS mode (Infrastructure, Managed) | 106 | + BSS mode (Infrastructure, Managed) |
51 | + IBSS mode (Ad-Hoc) | 107 | + IBSS mode (Ad-Hoc) |
@@ -56,17 +112,27 @@ The current release (1.0.0) supports the following features: | |||
56 | + Full A rate support (2915 only) | 112 | + Full A rate support (2915 only) |
57 | + Transmit power control | 113 | + Transmit power control |
58 | + S state support (ACPI suspend/resume) | 114 | + S state support (ACPI suspend/resume) |
115 | |||
116 | The following features are currently enabled, but not officially | ||
117 | supported: | ||
118 | |||
119 | + WPA | ||
59 | + long/short preamble support | 120 | + long/short preamble support |
121 | + Monitor mode (aka RFMon) | ||
122 | |||
123 | The distinction between officially supported and enabled is a reflection | ||
124 | on the amount of validation and interoperability testing that has been | ||
125 | performed on a given feature. | ||
60 | 126 | ||
61 | 127 | ||
62 | 128 | ||
63 | 1.2. Command Line Parameters | 129 | 1.2. Command Line Parameters |
64 | ----------------------------------------------- | 130 | ----------------------------------------------- |
65 | 131 | ||
66 | Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless | 132 | Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless |
67 | 2915ABG Driver for Linux allows certain configuration options to be | 133 | 2915ABG Driver for Linux allows configuration options to be provided |
68 | provided as module parameters. The most common way to specify a module | 134 | as module parameters. The most common way to specify a module parameter |
69 | parameter is via the command line. | 135 | is via the command line. |
70 | 136 | ||
71 | The general form is: | 137 | The general form is: |
72 | 138 | ||
@@ -96,14 +162,18 @@ Where the supported parameter are: | |||
96 | 162 | ||
97 | debug | 163 | debug |
98 | If using a debug build, this is used to control the amount of debug | 164 | If using a debug build, this is used to control the amount of debug |
99 | info is logged. See the 'dval' and 'load' script for more info on | 165 | info is logged. See the 'dvals' and 'load' script for more info on |
100 | how to use this (the dval and load scripts are provided as part | 166 | how to use this (the dvals and load scripts are provided as part |
101 | of the ipw2200 development snapshot releases available from the | 167 | of the ipw2200 development snapshot releases available from the |
102 | SourceForge project at http://ipw2200.sf.net) | 168 | SourceForge project at http://ipw2200.sf.net) |
169 | |||
170 | led | ||
171 | Can be used to turn on experimental LED code. | ||
172 | 0 = Off, 1 = On. Default is 0. | ||
103 | 173 | ||
104 | mode | 174 | mode |
105 | Can be used to set the default mode of the adapter. | 175 | Can be used to set the default mode of the adapter. |
106 | 0 = Managed, 1 = Ad-Hoc | 176 | 0 = Managed, 1 = Ad-Hoc, 2 = Monitor |
107 | 177 | ||
108 | 178 | ||
109 | 1.3. Wireless Extension Private Methods | 179 | 1.3. Wireless Extension Private Methods |
@@ -164,8 +234,8 @@ The supported private methods are: | |||
164 | ----------------------------------------------- | 234 | ----------------------------------------------- |
165 | 235 | ||
166 | The Linux kernel provides a pseudo file system that can be used to | 236 | The Linux kernel provides a pseudo file system that can be used to |
167 | access various components of the operating system. The Intel(R) | 237 | access various components of the operating system. The Intel(R) |
168 | PRO/Wireless 2915ABG Driver for Linux exposes several configuration | 238 | PRO/Wireless 2915ABG Driver for Linux exposes several configuration |
169 | parameters through this mechanism. | 239 | parameters through this mechanism. |
170 | 240 | ||
171 | An entry in the sysfs can support reading and/or writing. You can | 241 | An entry in the sysfs can support reading and/or writing. You can |
@@ -184,13 +254,13 @@ You can set the debug level via: | |||
184 | 254 | ||
185 | Where $VALUE would be a number in the case of this sysfs entry. The | 255 | Where $VALUE would be a number in the case of this sysfs entry. The |
186 | input to sysfs files does not have to be a number. For example, the | 256 | input to sysfs files does not have to be a number. For example, the |
187 | firmware loader used by hotplug utilizes sysfs entries for transferring | 257 | firmware loader used by hotplug utilizes sysfs entries for transfering |
188 | the firmware image from user space into the driver. | 258 | the firmware image from user space into the driver. |
189 | 259 | ||
190 | The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries | 260 | The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries |
191 | at two levels -- driver level, which apply to all instances of the | 261 | at two levels -- driver level, which apply to all instances of the driver |
192 | driver (in the event that there are more than one device installed) and | 262 | (in the event that there are more than one device installed) and device |
193 | device level, which applies only to the single specific instance. | 263 | level, which applies only to the single specific instance. |
194 | 264 | ||
195 | 265 | ||
196 | 1.4.1 Driver Level Sysfs Helper Files | 266 | 1.4.1 Driver Level Sysfs Helper Files |
@@ -203,6 +273,7 @@ For the driver level files, look in /sys/bus/pci/drivers/ipw2200/ | |||
203 | This controls the same global as the 'debug' module parameter | 273 | This controls the same global as the 'debug' module parameter |
204 | 274 | ||
205 | 275 | ||
276 | |||
206 | 1.4.2 Device Level Sysfs Helper Files | 277 | 1.4.2 Device Level Sysfs Helper Files |
207 | ----------------------------------------------- | 278 | ----------------------------------------------- |
208 | 279 | ||
@@ -213,7 +284,7 @@ For the device level files, look in | |||
213 | For example: | 284 | For example: |
214 | /sys/bus/pci/drivers/ipw2200/0000:02:01.0 | 285 | /sys/bus/pci/drivers/ipw2200/0000:02:01.0 |
215 | 286 | ||
216 | For the device level files, see /sys/bus/pci/[drivers/ipw2200: | 287 | For the device level files, see /sys/bus/pci/drivers/ipw2200: |
217 | 288 | ||
218 | rf_kill | 289 | rf_kill |
219 | read - | 290 | read - |
@@ -231,8 +302,59 @@ For the device level files, see /sys/bus/pci/[drivers/ipw2200: | |||
231 | ucode | 302 | ucode |
232 | read-only access to the ucode version number | 303 | read-only access to the ucode version number |
233 | 304 | ||
305 | led | ||
306 | read - | ||
307 | 0 = LED code disabled | ||
308 | 1 = LED code enabled | ||
309 | write - | ||
310 | 0 = Disable LED code | ||
311 | 1 = Enable LED code | ||
312 | |||
313 | NOTE: The LED code has been reported to hang some systems when | ||
314 | running ifconfig and is therefore disabled by default. | ||
315 | |||
316 | |||
317 | 2. Ad-Hoc Networking | ||
318 | ----------------------------------------------- | ||
319 | |||
320 | When using a device in an Ad-Hoc network, it is useful to understand the | ||
321 | sequence and requirements for the driver to be able to create, join, or | ||
322 | merge networks. | ||
323 | |||
324 | The following attempts to provide enough information so that you can | ||
325 | have a consistent experience while using the driver as a member of an | ||
326 | Ad-Hoc network. | ||
327 | |||
328 | 2.1. Joining an Ad-Hoc Network | ||
329 | ----------------------------------------------- | ||
330 | |||
331 | The easiest way to get onto an Ad-Hoc network is to join one that | ||
332 | already exists. | ||
234 | 333 | ||
235 | 2. About the Version Numbers | 334 | 2.2. Creating an Ad-Hoc Network |
335 | ----------------------------------------------- | ||
336 | |||
337 | An Ad-Hoc networks is created using the syntax of the Wireless tool. | ||
338 | |||
339 | For Example: | ||
340 | iwconfig eth1 mode ad-hoc essid testing channel 2 | ||
341 | |||
342 | 2.3. Merging Ad-Hoc Networks | ||
343 | ----------------------------------------------- | ||
344 | |||
345 | |||
346 | 3. Interaction with Wireless Tools | ||
347 | ----------------------------------------------- | ||
348 | |||
349 | 3.1 iwconfig mode | ||
350 | ----------------------------------------------- | ||
351 | |||
352 | When configuring the mode of the adapter, all run-time configured parameters | ||
353 | are reset to the value used when the module was loaded. This includes | ||
354 | channels, rates, ESSID, etc. | ||
355 | |||
356 | |||
357 | 4. About the Version Numbers | ||
236 | ----------------------------------------------- | 358 | ----------------------------------------------- |
237 | 359 | ||
238 | Due to the nature of open source development projects, there are | 360 | Due to the nature of open source development projects, there are |
@@ -259,12 +381,23 @@ available as quickly as possible, unknown anomalies should be expected. | |||
259 | The major version number will be incremented when significant changes | 381 | The major version number will be incremented when significant changes |
260 | are made to the driver. Currently, there are no major changes planned. | 382 | are made to the driver. Currently, there are no major changes planned. |
261 | 383 | ||
384 | 5. Firmware installation | ||
385 | ---------------------------------------------- | ||
386 | |||
387 | The driver requires a firmware image, download it and extract the | ||
388 | files under /lib/firmware (or wherever your hotplug's firmware.agent | ||
389 | will look for firmware files) | ||
390 | |||
391 | The firmware can be downloaded from the following URL: | ||
262 | 392 | ||
263 | 3. Support | 393 | http://ipw2200.sf.net/ |
394 | |||
395 | |||
396 | 6. Support | ||
264 | ----------------------------------------------- | 397 | ----------------------------------------------- |
265 | 398 | ||
266 | For installation support of the 1.0.0 version, you can contact | 399 | For direct support of the 1.0.0 version, you can contact |
267 | http://supportmail.intel.com, or you can use the open source project | 400 | http://supportmail.intel.com, or you can use the open source project |
268 | support. | 401 | support. |
269 | 402 | ||
270 | For general information and support, go to: | 403 | For general information and support, go to: |
@@ -272,7 +405,7 @@ For general information and support, go to: | |||
272 | http://ipw2200.sf.net/ | 405 | http://ipw2200.sf.net/ |
273 | 406 | ||
274 | 407 | ||
275 | 4. License | 408 | 7. License |
276 | ----------------------------------------------- | 409 | ----------------------------------------------- |
277 | 410 | ||
278 | Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved. | 411 | Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved. |
@@ -297,4 +430,3 @@ For general information and support, go to: | |||
297 | James P. Ketrenos <ipw2100-admin@linux.intel.com> | 430 | James P. Ketrenos <ipw2100-admin@linux.intel.com> |
298 | Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 | 431 | Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 |
299 | 432 | ||
300 | |||
diff --git a/MAINTAINERS b/MAINTAINERS index d57c491212b1..c051f493d0dc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS | |||
@@ -1310,6 +1310,24 @@ M: john.ronciak@intel.com | |||
1310 | W: http://sourceforge.net/projects/e1000/ | 1310 | W: http://sourceforge.net/projects/e1000/ |
1311 | S: Supported | 1311 | S: Supported |
1312 | 1312 | ||
1313 | INTEL PRO/WIRELESS 2100 NETWORK CONNECTION SUPPORT | ||
1314 | P: Yi Zhu | ||
1315 | M: yi.zhu@intel.com | ||
1316 | P: James Ketrenos | ||
1317 | M: jketreno@linux.intel.com | ||
1318 | L: http://lists.sourceforge.net/mailman/listinfo/ipw2100-devel | ||
1319 | W: http://ipw2100.sourceforge.net | ||
1320 | S: Supported | ||
1321 | |||
1322 | INTEL PRO/WIRELESS 2915ABG NETWORK CONNECTION SUPPORT | ||
1323 | P: Yi Zhu | ||
1324 | M: yi.zhu@intel.com | ||
1325 | P: James Ketrenos | ||
1326 | M: jketreno@linux.intel.com | ||
1327 | L: http://lists.sourceforge.net/mailman/listinfo/ipw2100-devel | ||
1328 | W: http://ipw2200.sourceforge.net | ||
1329 | S: Supported | ||
1330 | |||
1313 | IOC3 DRIVER | 1331 | IOC3 DRIVER |
1314 | P: Ralf Baechle | 1332 | P: Ralf Baechle |
1315 | M: ralf@linux-mips.org | 1333 | M: ralf@linux-mips.org |