slp/linux-wlan-ng
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reworded the USB reset stuff.

Browse source
This commit is contained in:
mark 2001-12-12 00:37:33 +00:00
parent 54bdf3882a
commit 3afc9bdef7
1 changed files with 27 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
README
View file

@ -307,15 +307,32 @@ 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>'
IMPORTANT: Due to an issue with the current firmware in Prism USB devices,
the driver must do a port reset (which is normally handled by usbcore). Some
usb low-level drivers don't like this, they see it as a new device connect.
When that happens things go very awry, possibly crashing and/or hanging the
machine. Unfortunately, there's nothing we can do about it until new firmware
becomes available. The good news is that the new firmware is coming, we just
don't know when it will be available. When it does become available,
remove the "prism2_doreset" on the modprobe command line above and everything
should work just peachy.
NOTE: USB devices can use the /etc/init.d/wlan script for initialization.
Integration with usbmgr/hotplug is still a TODO item.
IMPORTANT: Due to an issue with the current firmware in Prism USB devices,
the driver must do a port reset (which is normally handled by usbcore).
Some usb low-level drivers don't like this, they see it 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.
Unfortunately, there's nothing we can do about it until new firmware
becomes available. The good news is that the firmware developers are aware
of the problem, they have a fix, and the new firmware is coming, we just
don't know precisely when it will be available. It all depends on how quickly
they can get it through their QA process. When it does become available,
install it in your device using the Windows firmware update utility,
remove the "prism2_doreset" on the modprobe command line above and everything
will work just peachy.