Documentaion updates.

origin
solomon 21 years ago
parent f538e687e7
commit 771e817a59
  1. 78
      README
  2. 4
      TODO
  3. 8
      doc/config.linux-wlan-ng

@ -77,19 +77,16 @@ This release was tested on the following configurations:
Intel:
Kernel | pcmcia_cs | Distribution | Device Types
-------+-----------+--------------+---------------------------------------
2.2.20 | 3.1.29 | Debian woody | Prism2-PCMCIA-PFlash
| | | Prism2.5-PCMCIA-PFlash
| | | Prism2.5-PCI-PFlash
| | | Prism3-PCMCIA-PFlash
-------+-----------+--------------+---------------------------------------
2.4.17 | 3.1.31 | Debian woody | Prism2-PCMCIA-PFlash
2.4.18 | 3.1.31 | Debian woody | Prism2-PCMCIA-PFlash
| | | Prism2.5-PCMCIA-PFlash
| | | Prism2.5-PCI-PFlash
| | | Prism2.5-USB-PFlash
| | | Prism3-PCMCIA-PFlash
-------+-----------+--------------+---------------------------------------
2.4.19 | 3.2.0 | Redhat 7.2 | Prism2.5-PCI-PFlash
| | | Prism2.5-USB-PFlash
| | | Prism2.5-USB-PFlash
| | | Prism2-PCMCIA-PFlash
| | | Prism2.5-PCMCIA-PFlash
PowerPC:
Kernel | pcmcia_cs | Distribution | Device Types
@ -97,17 +94,16 @@ PowerPC:
2.2.13 | 3.1.10 | Custom | Prism2-PCMCIA-PFlash
| | | Prism2.5-PCMCIA-PFlash
| | | Prism3-PCMCIA-PFlash
-------+-----------+--------------+---------------------------------------
2.4.19 | 3.2.1 | Custom | Prism2-PCMCIA-PFlash
| | | Prism2.5-PCMCIA-PFlash
| | | Prism3-PCMCIA-PFlash
=======================================================================
Build Instructions:
NOTE: You may not need to build at all. Check the linux-wlan ftp site
for binary packages built by AVS. At the time of this writing the
following targets were supported:
RedHat 7.1
RedHat 7.2
Mandrake 8.1
NOTE: You may not need to build at all. Binary packages are
available for various distributions. See the FAQ for where to go.
NOTE: This release supports building four different drivers:
@ -138,12 +134,6 @@ To build linux-wlan-ng you will need:
- If you are building a driver for a PCMCIA card, you will also need
the configured PCMCIA source code for the pcmcia_cs subsystem you
are currently running.
- Note that AVS does not test with the kernel pcmcia support code,
we _always_ use the pcmcia-cs package with kernel pcmcia
completely disabled. CAREFUL: it is very easy to accidentally
enable the kernel pcmcia code, if you select _any_ of the
individual pcmcia devices in the various kernel config submenus,
kernel pcmcia will be selected.
Building linux-wlan-ng:
@ -156,16 +146,7 @@ Building linux-wlan-ng:
prism2_plx, or prism2_usb drivers you don't need the pcmcia-cs
source tree.
3) To clean up any unwanted files accidentally included in the tar package,
run 'make clean'. If make clean behaves badly (infinite loop, for
example), you may have a date/time mismatch. Run the command:
find . -type f -exec touch {} \;
to fix the date&time stamps, then run 'make clean' again.
4) To configure the linux-wlan-ng package, run 'make config'. The
3) To configure the linux-wlan-ng package, run 'make config'. The
following set of questions will be asked. The default answer is in
braces (e.g. []). Just press <Enter> to select the default answer:
@ -203,14 +184,6 @@ Building linux-wlan-ng:
change it here. If the "_cs" driver is not selected, this
prompt will not appear.
- Build for Kernel PCMCIA? (y/n) [n]:
If the "_cs" driver is selected, we need to know if you are
intending to use the kernel pcmcia code rather than pcmcia_cs.
This prompt will not appear if the "_cs" driver is not selected.
NOTE: AVS in-house testing is done almost exclusively using the
pcmcia_cs package with kernel pcmcia disabled. Therefore,
your results with kernel pcmcia may vary.
- PCMCIA script directory [/etc/pcmcia]:
If the "_cs" driver is selected, this prompt allows you to
change the location where the pcmcia scripts will be installed.
@ -228,11 +201,6 @@ Building linux-wlan-ng:
with, and the new kernel has a different version string, you will
need to change this value.
- Target Architecture? (i386, ppc, or alpha) [i386]:
On some targets, we can't identify the target processor from
compiler settings or predefined symbols. Therefore, we need an
explicit setting that identifies the target CPU.
- Prefix for build host compiler? (rarely needed) []:
When cross-compiling or using different compilers for kernel and
user-mode software, it is sometimes (but rarely) necessary to
@ -304,7 +272,7 @@ A) You must make sure that the drivers get loaded at boot time and that the
Also, don't forget to set up your resolv.conf to point at your DNS server.
B) If you are daring, you can try out the rc.wlan and wlan.conf scripts.
B) Alternatively you can try out the rc.wlan and wlan.conf scripts.
They do work, and they are installed into your */init.d directory
and /etc directory. We don't currently create the soft-link from
the runlevel directory to the wlan startup script because the
@ -329,27 +297,17 @@ E) Run 'wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem'
to enable the MAC in Infrastructure Station mode.
F) Run 'ifconfig wlan0 <your IP address>'
NOTE: USB devices can use the /etc/init.d/wlan script for initialization.
Integration with usbmgr/hotplug is still a TODO item.
NOTE: USB devices currently integrated into the hotplug subsystem, and
use the /etc/wlan.conf configuration file.
IMPORTANT: Due to an issue with the current firmware in Prism USB
devices, the driver must usually do a port reset (which is normally
handled by usbcore).
Some usb low-level drivers don't like this, they see the reset as a
new device connect (of something that's _already_ in the connected
state). When that happens things go very awry, possibly crashing
and/or hanging the machine.
Some low-level drivers handle it just fine.
Since it appears to be a combination of the underlying USB host hardware
_and_ the usb low-level driver _and_ the linux usb version, I haven't been able
to put together a description of precisely which hardware/software will work.
Some of my hardware here in the lab works, some hardware (with exactly the
same software) does not.
You will have to experiment on your own.
Some combinations of usb low-level drivers, kernel releases, and
hardware don't like this, and usually end up generating a kernel OOPS.
newer kernels are much better in this regard. In particular, Intel usb
controllers are the most trouble-prone.
Unfortunately, there's nothing we can do about it until new firmware
becomes available. The good news is that the firmware developers are aware

@ -43,6 +43,9 @@
* --------------------------------------------------------------------
Linux WLAN NG TODO
- Make the command-completion interrupt driven vs busywaiting.
- Possibly hook up DMA on the Rx side for PCI devices
- Further investigate lingering SMP issues
- Add a query of the ifstate.
- Move all of the wireless extensions work up to p80211 so that the new
MACs will get wireless extensions support for free!
@ -111,4 +114,3 @@ Linux WLAN NG TODO
- man pages
- Add a HOWTO document for users
- Add a HOWTO document for programmers
- Review 'make config' for additional options and validation

@ -145,6 +145,14 @@ is used, the WEP keys must be present.
dot11PrivacyInvoked=false
Set this variable to "true" to enable the WEP support.
lnxreq_hostWEPEncrypt=false
lnxreq_hostWEPDecrypt=false
Set these to true if you want WEP to be handled by the driver
instead of the hardware. The only downside of this is that it
takes a bit of CPU time and you lose the ability to handle
fragmentation. However, with prism2 cards, you should see a
performance boost, and with prism2.5 cards, this may avoid lockups.
dot11WEPDefaultKeyID=1
This variable identifies which of the WEP keys is the default
key used for all transmits from this station. In some

Loading…
Cancel
Save