Skip to content

L
linux
Commit c81f1957 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab Committed by David S. Miller
Browse files
Options

docs: networking: device drivers: convert intel/ipw2200.txt to ReST 

- add SPDX header;
- adjust titles and chapters, adding proper markups;
- comment out text-only TOC from html/pdf output;
- use copyright symbol;
- use :field: markup;
- mark code blocks and literals as such;
- mark tables as such;
- adjust identation, whitespaces and blank lines where needed;
- add to networking/index.rst.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent cf7eba49
Hide whitespace changes
Inline Side-by-side
Showing with 237 additions and 182 deletions
Documentation/networking/device_drivers/index.rst
View file @ c81f1957
...@@ -40,6 +40,7 @@ Contents: ...@@ -40,6 +40,7 @@ Contents:
freescale/dpaa freescale/dpaa
freescale/gianfar freescale/gianfar
intel/ipw2100 intel/ipw2100
intel/ipw2200
.. only:: subproject and html .. only:: subproject and html
......
Documentation/networking/device_drivers/intel/ipw2200.txt → Documentation/networking/device_drivers/intel/ipw2200.rst
View file @ c81f1957
.. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
Intel(R) PRO/Wireless 2915ABG Driver for Linux in support of: ==============================================
Intel(R) PRO/Wireless 2915ABG Driver for Linux
==============================================
Intel(R) PRO/Wireless 2200BG Network Connection
Intel(R) PRO/Wireless 2915ABG Network Connection Support for:
- Intel(R) PRO/Wireless 2200BG Network Connection
- Intel(R) PRO/Wireless 2915ABG Network Connection
Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R) Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R)
PRO/Wireless 2200BG Driver for Linux is a unified driver that works on PRO/Wireless 2200BG Driver for Linux is a unified driver that works on
...@@ -10,37 +17,37 @@ both hardware adapters listed above. In this document the Intel(R) ...@@ -10,37 +17,37 @@ both hardware adapters listed above. In this document the Intel(R)
PRO/Wireless 2915ABG Driver for Linux will be used to reference the PRO/Wireless 2915ABG Driver for Linux will be used to reference the
unified driver. unified driver.
Copyright (C) 2004-2006, Intel Corporation Copyright |copy| 2004-2006, Intel Corporation
README.ipw2200 README.ipw2200
Version: 1.1.2 :Version: 1.1.2
Date : March 30, 2006 :Date: March 30, 2006
Index .. Index
-----------------------------------------------
0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
1. Introduction
1.1. Overview of features
1.2. Module parameters
1.3. Wireless Extension Private Methods
1.4. Sysfs Helper Files
1.5. Supported channels
2. Ad-Hoc Networking
3. Interacting with Wireless Tools
3.1. iwconfig mode
3.2. iwconfig sens
4. About the Version Numbers
5. Firmware installation
6. Support
7. License
0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
1. Introduction
1.1. Overview of features
1.2. Module parameters
1.3. Wireless Extension Private Methods
1.4. Sysfs Helper Files
1.5. Supported channels
2. Ad-Hoc Networking
3. Interacting with Wireless Tools
3.1. iwconfig mode
3.2. iwconfig sens
4. About the Version Numbers
5. Firmware installation
6. Support
7. License
0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
-----------------------------------------------
Important Notice FOR ALL USERS OR DISTRIBUTORS!!!! 0. IMPORTANT INFORMATION BEFORE USING THIS DRIVER
=================================================
Important Notice FOR ALL USERS OR DISTRIBUTORS!!!!
Intel wireless LAN adapters are engineered, manufactured, tested, and Intel wireless LAN adapters are engineered, manufactured, tested, and
quality checked to ensure that they meet all necessary local and quality checked to ensure that they meet all necessary local and
...@@ -56,7 +63,7 @@ product is granted. Intel's wireless LAN's EEPROM, firmware, and ...@@ -56,7 +63,7 @@ product is granted. Intel's wireless LAN's EEPROM, firmware, and
software driver are designed to carefully control parameters that affect software driver are designed to carefully control parameters that affect
radio operation and to ensure electromagnetic compliance (EMC). These radio operation and to ensure electromagnetic compliance (EMC). These
parameters include, without limitation, RF power, spectrum usage, parameters include, without limitation, RF power, spectrum usage,
channel scanning, and human exposure. channel scanning, and human exposure.
For these reasons Intel cannot permit any manipulation by third parties For these reasons Intel cannot permit any manipulation by third parties
of the software provided in binary format with the wireless WLAN of the software provided in binary format with the wireless WLAN
...@@ -70,7 +77,7 @@ no liability, under any theory of liability for any issues associated ...@@ -70,7 +77,7 @@ no liability, under any theory of liability for any issues associated
with the modified products, including without limitation, claims under with the modified products, including without limitation, claims under
the warranty and/or issues arising from regulatory non-compliance, and the warranty and/or issues arising from regulatory non-compliance, and
(iii) Intel will not provide or be required to assist in providing (iii) Intel will not provide or be required to assist in providing
support to any third parties for such modified products. support to any third parties for such modified products.
Note: Many regulatory agencies consider Wireless LAN adapters to be Note: Many regulatory agencies consider Wireless LAN adapters to be
modules, and accordingly, condition system-level regulatory approval modules, and accordingly, condition system-level regulatory approval
...@@ -78,23 +85,24 @@ upon receipt and review of test data documenting that the antennas and ...@@ -78,23 +85,24 @@ upon receipt and review of test data documenting that the antennas and
system configuration do not cause the EMC and radio operation to be system configuration do not cause the EMC and radio operation to be
non-compliant. non-compliant.
The drivers available for download from SourceForge are provided as a The drivers available for download from SourceForge are provided as a
part of a development project. Conformance to local regulatory part of a development project. Conformance to local regulatory
requirements is the responsibility of the individual developer. As requirements is the responsibility of the individual developer. As
such, if you are interested in deploying or shipping a driver as part of such, if you are interested in deploying or shipping a driver as part of
solution intended to be used for purposes other than development, please solution intended to be used for purposes other than development, please
obtain a tested driver from Intel Customer Support at: obtain a tested driver from Intel Customer Support at:
http://support.intel.com http://support.intel.com
1. Introduction 1. Introduction
----------------------------------------------- ===============
The following sections attempt to provide a brief introduction to using
The following sections attempt to provide a brief introduction to using
the Intel(R) PRO/Wireless 2915ABG Driver for Linux. the Intel(R) PRO/Wireless 2915ABG Driver for Linux.
This document is not meant to be a comprehensive manual on This document is not meant to be a comprehensive manual on
understanding or using wireless technologies, but should be sufficient understanding or using wireless technologies, but should be sufficient
to get you moving without wires on Linux. to get you moving without wires on Linux.
For information on building and installing the driver, see the INSTALL For information on building and installing the driver, see the INSTALL
...@@ -102,14 +110,14 @@ file. ...@@ -102,14 +110,14 @@ file.
1.1. Overview of Features 1.1. Overview of Features
----------------------------------------------- -------------------------
The current release (1.1.2) supports the following features: The current release (1.1.2) supports the following features:
+ BSS mode (Infrastructure, Managed) + BSS mode (Infrastructure, Managed)
+ IBSS mode (Ad-Hoc) + IBSS mode (Ad-Hoc)
+ WEP (OPEN and SHARED KEY mode) + WEP (OPEN and SHARED KEY mode)
+ 802.1x EAP via wpa_supplicant and xsupplicant + 802.1x EAP via wpa_supplicant and xsupplicant
+ Wireless Extension support + Wireless Extension support
+ Full B and G rate support (2200 and 2915) + Full B and G rate support (2200 and 2915)
+ Full A rate support (2915 only) + Full A rate support (2915 only)
+ Transmit power control + Transmit power control
...@@ -122,102 +130,107 @@ supported: ...@@ -122,102 +130,107 @@ supported:
+ long/short preamble support + long/short preamble support
+ Monitor mode (aka RFMon) + Monitor mode (aka RFMon)
The distinction between officially supported and enabled is a reflection The distinction between officially supported and enabled is a reflection
on the amount of validation and interoperability testing that has been on the amount of validation and interoperability testing that has been
performed on a given feature. performed on a given feature.
1.2. Command Line Parameters 1.2. Command Line Parameters
----------------------------------------------- ----------------------------
Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless Like many modules used in the Linux kernel, the Intel(R) PRO/Wireless
2915ABG Driver for Linux allows configuration options to be provided 2915ABG Driver for Linux allows configuration options to be provided
as module parameters. The most common way to specify a module parameter as module parameters. The most common way to specify a module parameter
is via the command line. is via the command line.
The general form is: The general form is::
% modprobe ipw2200 parameter=value % modprobe ipw2200 parameter=value
Where the supported parameter are: Where the supported parameter are:
associate associate
Set to 0 to disable the auto scan-and-associate functionality of the Set to 0 to disable the auto scan-and-associate functionality of the
driver. If disabled, the driver will not attempt to scan driver. If disabled, the driver will not attempt to scan
for and associate to a network until it has been configured with for and associate to a network until it has been configured with
one or more properties for the target network, for example configuring one or more properties for the target network, for example configuring
the network SSID. Default is 0 (do not auto-associate) the network SSID. Default is 0 (do not auto-associate)
Example: % modprobe ipw2200 associate=0 Example: % modprobe ipw2200 associate=0
auto_create auto_create
Set to 0 to disable the auto creation of an Ad-Hoc network Set to 0 to disable the auto creation of an Ad-Hoc network
matching the channel and network name parameters provided. matching the channel and network name parameters provided.
Default is 1. Default is 1.
channel channel
channel number for association. The normal method for setting channel number for association. The normal method for setting
the channel would be to use the standard wireless tools the channel would be to use the standard wireless tools
(i.e. `iwconfig eth1 channel 10`), but it is useful sometimes (i.e. `iwconfig eth1 channel 10`), but it is useful sometimes
to set this while debugging. Channel 0 means 'ANY' to set this while debugging. Channel 0 means 'ANY'
debug debug
If using a debug build, this is used to control the amount of debug If using a debug build, this is used to control the amount of debug
info is logged. See the 'dvals' and 'load' script for more info on info is logged. See the 'dvals' and 'load' script for more info on
how to use this (the dvals and load scripts are provided as part how to use this (the dvals and load scripts are provided as part
of the ipw2200 development snapshot releases available from the of the ipw2200 development snapshot releases available from the
SourceForge project at http://ipw2200.sf.net) SourceForge project at http://ipw2200.sf.net)
led led
Can be used to turn on experimental LED code. Can be used to turn on experimental LED code.
0 = Off, 1 = On. Default is 1. 0 = Off, 1 = On. Default is 1.
mode mode
Can be used to set the default mode of the adapter. Can be used to set the default mode of the adapter.
0 = Managed, 1 = Ad-Hoc, 2 = Monitor 0 = Managed, 1 = Ad-Hoc, 2 = Monitor
1.3. Wireless Extension Private Methods 1.3. Wireless Extension Private Methods
----------------------------------------------- ---------------------------------------
As an interface designed to handle generic hardware, there are certain As an interface designed to handle generic hardware, there are certain
capabilities not exposed through the normal Wireless Tool interface. As capabilities not exposed through the normal Wireless Tool interface. As
such, a provision is provided for a driver to declare custom, or such, a provision is provided for a driver to declare custom, or
private, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux private, methods. The Intel(R) PRO/Wireless 2915ABG Driver for Linux
defines several of these to configure various settings. defines several of these to configure various settings.
The general form of using the private wireless methods is: The general form of using the private wireless methods is::
% iwpriv $IFNAME method parameters % iwpriv $IFNAME method parameters
Where $IFNAME is the interface name the device is registered with Where $IFNAME is the interface name the device is registered with
(typically eth1, customized via one of the various network interface (typically eth1, customized via one of the various network interface
name managers, such as ifrename) name managers, such as ifrename)
The supported private methods are: The supported private methods are:
get_mode get_mode
Can be used to report out which IEEE mode the driver is Can be used to report out which IEEE mode the driver is
configured to support. Example: configured to support. Example:
% iwpriv eth1 get_mode % iwpriv eth1 get_mode
eth1 get_mode:802.11bg (6) eth1 get_mode:802.11bg (6)
set_mode set_mode
Can be used to configure which IEEE mode the driver will Can be used to configure which IEEE mode the driver will
support. support.
Usage::
% iwpriv eth1 set_mode {mode}
Usage:
% iwpriv eth1 set_mode {mode}
Where {mode} is a number in the range 1-7: Where {mode} is a number in the range 1-7:
== =====================
1 802.11a (2915 only) 1 802.11a (2915 only)
2 802.11b 2 802.11b
3 802.11ab (2915 only) 3 802.11ab (2915 only)
4 802.11g 4 802.11g
5 802.11ag (2915 only) 5 802.11ag (2915 only)
6 802.11bg 6 802.11bg
7 802.11abg (2915 only) 7 802.11abg (2915 only)
== =====================
get_preamble get_preamble
Can be used to report configuration of preamble length. Can be used to report configuration of preamble length.
...@@ -225,99 +238,123 @@ The supported private methods are: ...@@ -225,99 +238,123 @@ The supported private methods are:
set_preamble set_preamble
Can be used to set the configuration of preamble length: Can be used to set the configuration of preamble length:
Usage: Usage::
% iwpriv eth1 set_preamble {mode}
% iwpriv eth1 set_preamble {mode}
Where {mode} is one of: Where {mode} is one of:
== ========================================
1 Long preamble only 1 Long preamble only
0 Auto (long or short based on connection) 0 Auto (long or short based on connection)
== ========================================
1.4. Sysfs Helper Files: 1.4. Sysfs Helper Files
----------------------------------------------- -----------------------
The Linux kernel provides a pseudo file system that can be used to The Linux kernel provides a pseudo file system that can be used to
access various components of the operating system. The Intel(R) access various components of the operating system. The Intel(R)
PRO/Wireless 2915ABG Driver for Linux exposes several configuration PRO/Wireless 2915ABG Driver for Linux exposes several configuration
parameters through this mechanism. parameters through this mechanism.
An entry in the sysfs can support reading and/or writing. You can An entry in the sysfs can support reading and/or writing. You can
typically query the contents of a sysfs entry through the use of cat, typically query the contents of a sysfs entry through the use of cat,
and can set the contents via echo. For example: and can set the contents via echo. For example::
% cat /sys/bus/pci/drivers/ipw2200/debug_level % cat /sys/bus/pci/drivers/ipw2200/debug_level
Will report the current debug level of the driver's logging subsystem Will report the current debug level of the driver's logging subsystem
(only available if CONFIG_IPW2200_DEBUG was configured when the driver (only available if CONFIG_IPW2200_DEBUG was configured when the driver
was built). was built).
You can set the debug level via: You can set the debug level via::
% echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level % echo $VALUE > /sys/bus/pci/drivers/ipw2200/debug_level
Where $VALUE would be a number in the case of this sysfs entry. The Where $VALUE would be a number in the case of this sysfs entry. The
input to sysfs files does not have to be a number. For example, the input to sysfs files does not have to be a number. For example, the
firmware loader used by hotplug utilizes sysfs entries for transferring firmware loader used by hotplug utilizes sysfs entries for transferring
the firmware image from user space into the driver. the firmware image from user space into the driver.
The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries The Intel(R) PRO/Wireless 2915ABG Driver for Linux exposes sysfs entries
at two levels -- driver level, which apply to all instances of the driver at two levels -- driver level, which apply to all instances of the driver
(in the event that there are more than one device installed) and device (in the event that there are more than one device installed) and device
level, which applies only to the single specific instance. level, which applies only to the single specific instance.
1.4.1 Driver Level Sysfs Helper Files 1.4.1 Driver Level Sysfs Helper Files
----------------------------------------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For the driver level files, look in /sys/bus/pci/drivers/ipw2200/ For the driver level files, look in /sys/bus/pci/drivers/ipw2200/
debug_level debug_level
This controls the same global as the 'debug' module parameter This controls the same global as the 'debug' module parameter
1.4.2 Device Level Sysfs Helper Files 1.4.2 Device Level Sysfs Helper Files
----------------------------------------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For the device level files, look in::
For the device level files, look in
/sys/bus/pci/drivers/ipw2200/{PCI-ID}/ /sys/bus/pci/drivers/ipw2200/{PCI-ID}/
For example: For example:::
/sys/bus/pci/drivers/ipw2200/0000:02:01.0 /sys/bus/pci/drivers/ipw2200/0000:02:01.0
For the device level files, see /sys/bus/pci/drivers/ipw2200: For the device level files, see /sys/bus/pci/drivers/ipw2200:
rf_kill rf_kill
read - read -
0 = RF kill not enabled (radio on)
1 = SW based RF kill active (radio off) == =========================================
2 = HW based RF kill active (radio off) 0 RF kill not enabled (radio on)
3 = Both HW and SW RF kill active (radio off) 1 SW based RF kill active (radio off)
2 HW based RF kill active (radio off)
3 Both HW and SW RF kill active (radio off)
== =========================================
write - write -
0 = If SW based RF kill active, turn the radio back on
1 = If radio is on, activate SW based RF kill
NOTE: If you enable the SW based RF kill and then toggle the HW == ==================================================
based RF kill from ON -> OFF -> ON, the radio will NOT come back on 0 If SW based RF kill active, turn the radio back on
1 If radio is on, activate SW based RF kill
ucode == ==================================================
.. note::
If you enable the SW based RF kill and then toggle the HW
based RF kill from ON -> OFF -> ON, the radio will NOT come back on
ucode
read-only access to the ucode version number read-only access to the ucode version number
led led
read - read -
0 = LED code disabled
1 = LED code enabled == =================
0 LED code disabled
1 LED code enabled
== =================
write - write -
0 = Disable LED code
1 = Enable LED code
NOTE: The LED code has been reported to hang some systems when == ================
running ifconfig and is therefore disabled by default. 0 Disable LED code
1 Enable LED code
== ================
.. note::
The LED code has been reported to hang some systems when
running ifconfig and is therefore disabled by default.
1.5. Supported channels 1.5. Supported channels
----------------------------------------------- -----------------------
Upon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a Upon loading the Intel(R) PRO/Wireless 2915ABG Driver for Linux, a
message stating the detected geography code and the number of 802.11 message stating the detected geography code and the number of 802.11
...@@ -326,44 +363,59 @@ channels supported by the card will be displayed in the log. ...@@ -326,44 +363,59 @@ channels supported by the card will be displayed in the log.
The geography code corresponds to a regulatory domain as shown in the The geography code corresponds to a regulatory domain as shown in the
table below. table below.
Supported channels +------+----------------------------+--------------------+
Code Geography 802.11bg 802.11a | | | Supported channels |
| Code | Geography +----------+---------+
--- Restricted 11 0 | | | 802.11bg | 802.11a |
ZZF Custom US/Canada 11 8 +======+============================+==========+=========+
ZZD Rest of World 13 0 | --- | Restricted | 11 | 0 |
ZZA Custom USA & Europe & High 11 13 +------+----------------------------+----------+---------+
ZZB Custom NA & Europe 11 13 | ZZF | Custom US/Canada | 11 | 8 |
ZZC Custom Japan 11 4 +------+----------------------------+----------+---------+
ZZM Custom 11 0 | ZZD | Rest of World | 13 | 0 |
ZZE Europe 13 19 +------+----------------------------+----------+---------+
ZZJ Custom Japan 14 4 | ZZA | Custom USA & Europe & High | 11 | 13 |
ZZR Rest of World 14 0 +------+----------------------------+----------+---------+
ZZH High Band 13 4 | ZZB | Custom NA & Europe | 11 | 13 |
ZZG Custom Europe 13 4 +------+----------------------------+----------+---------+
ZZK Europe 13 24 | ZZC | Custom Japan | 11 | 4 |
ZZL Europe 11 13 +------+----------------------------+----------+---------+
| ZZM | Custom | 11 | 0 |
+------+----------------------------+----------+---------+
2. Ad-Hoc Networking | ZZE | Europe | 13 | 19 |
----------------------------------------------- +------+----------------------------+----------+---------+
| ZZJ | Custom Japan | 14 | 4 |
When using a device in an Ad-Hoc network, it is useful to understand the +------+----------------------------+----------+---------+
sequence and requirements for the driver to be able to create, join, or | ZZR | Rest of World | 14 | 0 |
+------+----------------------------+----------+---------+
| ZZH | High Band | 13 | 4 |
+------+----------------------------+----------+---------+
| ZZG | Custom Europe | 13 | 4 |
+------+----------------------------+----------+---------+
| ZZK | Europe | 13 | 24 |
+------+----------------------------+----------+---------+
| ZZL | Europe | 11 | 13 |
+------+----------------------------+----------+---------+
2. Ad-Hoc Networking
=====================
When using a device in an Ad-Hoc network, it is useful to understand the
sequence and requirements for the driver to be able to create, join, or
merge networks. merge networks.
The following attempts to provide enough information so that you can The following attempts to provide enough information so that you can
have a consistent experience while using the driver as a member of an have a consistent experience while using the driver as a member of an
Ad-Hoc network. Ad-Hoc network.
2.1. Joining an Ad-Hoc Network 2.1. Joining an Ad-Hoc Network
----------------------------------------------- ------------------------------
The easiest way to get onto an Ad-Hoc network is to join one that The easiest way to get onto an Ad-Hoc network is to join one that
already exists. already exists.
2.2. Creating an Ad-Hoc Network 2.2. Creating an Ad-Hoc Network
----------------------------------------------- -------------------------------
An Ad-Hoc networks is created using the syntax of the Wireless tool. An Ad-Hoc networks is created using the syntax of the Wireless tool.
...@@ -371,21 +423,21 @@ For Example: ...@@ -371,21 +423,21 @@ For Example:
iwconfig eth1 mode ad-hoc essid testing channel 2 iwconfig eth1 mode ad-hoc essid testing channel 2
2.3. Merging Ad-Hoc Networks 2.3. Merging Ad-Hoc Networks
----------------------------------------------- ----------------------------
3. Interaction with Wireless Tools 3. Interaction with Wireless Tools
----------------------------------------------- ==================================
3.1 iwconfig mode 3.1 iwconfig mode
----------------------------------------------- -----------------
When configuring the mode of the adapter, all run-time configured parameters When configuring the mode of the adapter, all run-time configured parameters
are reset to the value used when the module was loaded. This includes are reset to the value used when the module was loaded. This includes
channels, rates, ESSID, etc. channels, rates, ESSID, etc.
3.2 iwconfig sens 3.2 iwconfig sens
----------------------------------------------- -----------------
The 'iwconfig ethX sens XX' command will not set the signal sensitivity The 'iwconfig ethX sens XX' command will not set the signal sensitivity
threshold, as described in iwconfig documentation, but rather the number threshold, as described in iwconfig documentation, but rather the number
...@@ -394,35 +446,35 @@ to another access point. At the same time, it will set the disassociation ...@@ -394,35 +446,35 @@ to another access point. At the same time, it will set the disassociation
threshold to 3 times the given value. threshold to 3 times the given value.
4. About the Version Numbers 4. About the Version Numbers
----------------------------------------------- =============================
Due to the nature of open source development projects, there are Due to the nature of open source development projects, there are
frequently changes being incorporated that have not gone through frequently changes being incorporated that have not gone through
a complete validation process. These changes are incorporated into a complete validation process. These changes are incorporated into
development snapshot releases. development snapshot releases.
Releases are numbered with a three level scheme: Releases are numbered with a three level scheme:
major.minor.development major.minor.development
Any version where the 'development' portion is 0 (for example Any version where the 'development' portion is 0 (for example
1.0.0, 1.1.0, etc.) indicates a stable version that will be made 1.0.0, 1.1.0, etc.) indicates a stable version that will be made
available for kernel inclusion. available for kernel inclusion.
Any version where the 'development' portion is not a 0 (for Any version where the 'development' portion is not a 0 (for
example 1.0.1, 1.1.5, etc.) indicates a development version that is example 1.0.1, 1.1.5, etc.) indicates a development version that is
being made available for testing and cutting edge users. The stability being made available for testing and cutting edge users. The stability
and functionality of the development releases are not know. We make and functionality of the development releases are not know. We make
efforts to try and keep all snapshots reasonably stable, but due to the efforts to try and keep all snapshots reasonably stable, but due to the
frequency of their release, and the desire to get those releases frequency of their release, and the desire to get those releases
available as quickly as possible, unknown anomalies should be expected. available as quickly as possible, unknown anomalies should be expected.
The major version number will be incremented when significant changes The major version number will be incremented when significant changes
are made to the driver. Currently, there are no major changes planned. are made to the driver. Currently, there are no major changes planned.
5. Firmware installation 5. Firmware installation
---------------------------------------------- ========================
The driver requires a firmware image, download it and extract the The driver requires a firmware image, download it and extract the
files under /lib/firmware (or wherever your hotplug's firmware.agent files under /lib/firmware (or wherever your hotplug's firmware.agent
...@@ -433,40 +485,42 @@ The firmware can be downloaded from the following URL: ...@@ -433,40 +485,42 @@ The firmware can be downloaded from the following URL:
http://ipw2200.sf.net/ http://ipw2200.sf.net/
6. Support 6. Support
----------------------------------------------- ==========
For direct support of the 1.0.0 version, you can contact For direct support of the 1.0.0 version, you can contact
http://supportmail.intel.com, or you can use the open source project http://supportmail.intel.com, or you can use the open source project
support. support.
For general information and support, go to: For general information and support, go to:
http://ipw2200.sf.net/ http://ipw2200.sf.net/
7. License 7. License
----------------------------------------------- ==========
Copyright(c) 2003 - 2006 Intel Corporation. All rights reserved. Copyright |copy| 2003 - 2006 Intel Corporation. All rights reserved.
This program is free software; you can redistribute it and/or modify it This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License version 2 as under the terms of the GNU General Public License version 2 as
published by the Free Software Foundation. published by the Free Software Foundation.
This program is distributed in the hope that it will be useful, but WITHOUT This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
more details. more details.
You should have received a copy of the GNU General Public License along with You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 59 this program; if not, write to the Free Software Foundation, Inc., 59
Temple Place - Suite 330, Boston, MA 02111-1307, USA. Temple Place - Suite 330, Boston, MA 02111-1307, USA.
The full GNU General Public License is included in this distribution in the The full GNU General Public License is included in this distribution in the
file called LICENSE. file called LICENSE.
Contact Information: Contact Information:
James P. Ketrenos <ipw2100-admin@linux.intel.com> James P. Ketrenos <ipw2100-admin@linux.intel.com>
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497
MAINTAINERS
View file @ c81f1957
...@@ -8743,7 +8743,7 @@ M: Stanislav Yakovlev <stas.yakovlev@gmail.com> ...@@ -8743,7 +8743,7 @@ M: Stanislav Yakovlev <stas.yakovlev@gmail.com>
L: linux-wireless@vger.kernel.org L: linux-wireless@vger.kernel.org
S: Maintained S: Maintained
F: Documentation/networking/device_drivers/intel/ipw2100.rst F: Documentation/networking/device_drivers/intel/ipw2100.rst
F: Documentation/networking/device_drivers/intel/ipw2200.txt F: Documentation/networking/device_drivers/intel/ipw2200.rst
F: drivers/net/wireless/intel/ipw2x00/ F: drivers/net/wireless/intel/ipw2x00/
INTEL PSTATE DRIVER INTEL PSTATE DRIVER
......
drivers/net/wireless/intel/ipw2x00/Kconfig
View file @ c81f1957
...@@ -78,7 +78,7 @@ config IPW2200 ...@@ -78,7 +78,7 @@ config IPW2200
A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network
Connection adapters. Connection adapters.
See <file:Documentation/networking/device_drivers/intel/ipw2200.txt> See <file:Documentation/networking/device_drivers/intel/ipw2200.rst>
for information on the capabilities currently enabled in this for information on the capabilities currently enabled in this
driver and for tips for debugging issues and problems. driver and for tips for debugging issues and problems.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7