From: Jean-Francois Dive (jef_at_linuxbe.org)
Date: 2002-01-30 05:38:05 UTC
We are actually working on your driver and the tests shows up a very good start. We (off course) have
troubles and ideas. here they are:
- We have to have a support for PCI cards (not PLX) (in our case: Dlink 520) which have a Prismp 2.5
chipset. We are working on the integration with your code. and hope to get something soon.
- I have a more generic question about encryption support in your this driver:
--> why is it not supported in AP mode ? As far as i can see, the encryption is set and done
in the chipset itself, and the AP mode is software related and not hardware at all. Where is
the limitation ? Some simple tests (remove the check in the IOCTL) shows that when both peers
are in restricted encryption mode (one AP and one managed) , the association occurs properly, but not a single data frame
seems to appear in the AP code. Any leads in this ?
--> I cant make encryption work in ad-hoc mode either: as soon as i set the encryption mode
to restricted, i get an error like:
Jan 30 16:16:39 gardafou kernel: wlan0: hfa384x_cmd - timeout - reg=0x8001
Jan 30 16:16:39 gardafou kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110)
and then the chipset goes crazy, reset of the driver is the only solution.
These tests are done on 2.4.17, Dlkink DWL-650's ..
-> Jean-Francois Dive
This archive was generated by