X-Git-Url: http://git.osdn.net/view?p=android-x86%2Fexternal-wireless-tools.git;a=blobdiff_plain;f=wireless_tools%2FPCMCIA.txt;h=92255859294346efc28d32a482646617f8e3a84d;hp=0ac220dfdb01b9eb1ce2cf78cbd717a39b026913;hb=1b80ed8726aa0f9de14e4231e8d199e5e27ef533;hpb=92c266503ddec9d3bd219978c118a77a46dc12d4 diff --git a/wireless_tools/PCMCIA.txt b/wireless_tools/PCMCIA.txt index 0ac220d..9225585 100644 --- a/wireless_tools/PCMCIA.txt +++ b/wireless_tools/PCMCIA.txt @@ -1,3 +1,6 @@ + Pcmcia Wireless configuration + ----------------------------- + One of the most exciting thing having happen after release 20 is the addition of Wireless Extension support in the Pcmcia init scripts. Here is a quick intro on the subject... @@ -14,14 +17,22 @@ Raylink driver : The Raylink driver as of 1.70 doesn't support yet writable Wireless Extensions, so enabling wireless.opts on this driver will make thing worse. - -Pcmcia precompiled package : --------------------------- - The Pcmcia package part of many distributions, especially -those from Red-Hat, include some weird init scripts. Because of this, -the present feature won't work. - On the other hand, the Pcmcia package in source form from the -official Linux-Pcmcia web site will install the proper init scripts. + On the other hand, the latest version of the Raylink driver +accept Wireless Extensions at boot time, so the procedure described +below will work. + +Distribution specific notes : +--------------------------- + Most modern distributions don't use wireless.opts and have +their own procedure for wireless configuration, which is usually +compatible with their configuration tools and work for non-Pcmcia +devices. This is documented in DISTRIBUTIONS.txt. + The procedure described here will work only with the original +Pcmcia configuration scripts. If you use a precompiled package part of +a distributions, this is usually not the case (see above). + On the other hand, if you install the Pcmcia package in source +form from the official Linux-Pcmcia web site, it will install the +proper init scripts and those instructions will apply. Basic support : ------------- @@ -132,4 +143,18 @@ home,*,*,00:60:1D:*|home,*,*,00:02:2D:*) I guess you get the idea ;-) +More elaborated configurations : +------------------------------ + Some people may need some more complex configurations. For +example, you might want to do one of the following thing : + o cycle through a set of schemes + o autodetect the proper scheme + There is currently no support to do that. However, the +Wireless Tools package contains a tool called "iwgetid" that can help +in this job. The source code contains some hints on how to achieve the +above thing. + If you ever write such a package, please send me the URL. + Good luck ! + + Jean