From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Ketrenos Subject: [PATCH] ipw2100 v1.1.0 Date: Wed, 23 Mar 2005 17:32:29 -0600 Message-ID: <4241FC8D.40400@linux.intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------050204000700060403060604" To: netdev@oss.sgi.com Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org This is a multi-part message in MIME format. --------------050204000700060403060604 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ok, we recently pushed the latest version of the IPW2100 driver to a stable version. The last stable version was 1.0.0, which wasn't compatible with the latest ieee80211 subsystem currently in netdev-2.6. In addition to fixing to be compatible w/ the ieee80211 stack, 1.1.0 also includes quite a few fixes over what was in 1.0.0. Anyway, attached is the patch against netdev-2.6 (build tested w/ the tip of wireless-2.6) that adds ipw2100 1.1.0 to the tree. Please let me know your comments and feedback. I wasn't sure where to actually stick the driver's selection it in the Kconfig menu. Where its at now, it doesn't show up until you enable 'Generic IEEE 80211 subsystem', and then it shows up down under Wireless Lan entries. Any opposition to creating a Wireless Drivers under the Generic IEEE 80211 level and putting drivers using that stack into that location? In terms of the process used for validation on the ipw2100, our plan is to only push patches out for kernel mainline inclusion that have gone through internal regression testing. Kernel API migration changes aren't much of an issue, but any functionality changes or fixes would need to go into our development versions on SourceForge first before we would want them pushed into mainline (assuming we get this into netdev, and then pushed upstream...) I'll be sending an ipw2200-1.0.0 patch out soon. We also have some fixes for ieee80211 that have been incorporated into the latest development snapshots for the ipw2200 project that I'll send a patch out for. Thanks, James --------------050204000700060403060604 Content-Type: text/x-patch; name="netdev-2.6-ipw2100-1.1.0.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="netdev-2.6-ipw2100-1.1.0.patch" diff -Nur --exclude=RCS --exclude=CVS --exclude=SCCS --exclude=BitKeeper --exclude=ChangeSet netdev-2.6/Documentation/networking/README.ipw2100 ipw2100-2.6/Documentation/networking/README.ipw2100 --- netdev-2.6/Documentation/networking/README.ipw2100 1969-12-31 18:00:00 -06:00 +++ ipw2100-2.6/Documentation/networking/README.ipw2100 2005-03-23 13:13:50 -06:00 @@ -0,0 +1,246 @@ + +=========================== +Intel(R) PRO/Wireless 2100 Network Connection Driver for Linux +README.ipw2100 + +March 14, 2005 + +=========================== +Index +--------------------------- +0. Introduction +1. Release 1.1.0 Current Features +2. Command Line Parameters +3. Sysfs Helper Files +4. Radio Kill Switch +5. Dynamic Firmware +6. Power Management +7. Support +8. License + + +=========================== +0. Introduction +------------ ----- ----- ---- --- -- - + +This document provides a brief overview of the features supported by the +IPW2100 driver project. The main project website, where the latest +development version of the driver can be found, is: + + http://ipw2100.sourceforge.net + +There you can find the not only the latest releases, but also information about +potential fixes and patches, as well as links to the development mailing list +for the driver project. + + +=========================== +1. Release 1.1.0 Current Supported Features +--------------------------- +- Managed (BSS) and Ad-Hoc (IBSS) +- WEP (shared key and open) +- Wireless Tools support +- 802.1x (tested with XSupplicant 1.0.1) + +Enabled (but not supported) features: +- Monitor/RFMon mode +- WPA/WPA2 + +The distinction between officially supported and enabled is a reflection +on the amount of validation and interoperability testing that has been +performed on a given feature. + + +=========================== +2. Command Line Parameters +--------------------------- + +If the driver is built as a module, the following optional parameters are used +by entering them on the command line with the modprobe command using this +syntax: + + modprobe ipw2100 [