Prism2.5 BAP time out & bad performance

[jar at pcuf.fi]

Hello

Our configuration/performance:

wlan-client---------AP/bridge------wired--------PC

|--- 1) ---------------------------------------> 20-50 kB/s
<--- 2) ---------------------------------------| 400-500 kB/s
<---- 450 kB/s --------><------- 850 kB/s ----->

wlan-client:
============
PIII
Windows XP+Sp1
Orinoco Silver 11Mb/s + FW 8.72 + newest drivers

AP/bridge:
==========
P166 MMX
RH Linux 9 + 2.4.20-20.9 stock kernel
bride-utils 0.9.6-1 from courceforge
hostap-0.0.4/hostap_pci
3COM 3CRW696 Prism2.5
  FIRMWARE BASED WEP ENABLED
  NICID: id=0x8013 v1.0.0
  PRIID: id=0x0015 v1.1.0
  STAID: id=0x001f v1.4.9
3COM 3c509B NIC

PC:
============
PII
Windows NT 4.0+Sp6a
3COM 3c900 NIC

1) The performance between wlan-client<-->PC is not good.

2) The performace is good, BUT the wlan card resets itself countinously.
So that it looks like this:

NETDEV WATCHDOG: wlan0: transmit timed out
wlan0 Tx timed out! Resetting card
wlan0: CMD=010b EVSTAT=0000 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
wlan0: scheduled card reset
hostap_pci: wlan0: resetting card
wlan0: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x0190)
prism2_hw_init: initialized in 200 ms
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: hfa384x_setup_bap - timeout after
wlan0: prism2_tx - to BAP0 failed
wlan0: hfa384x_setup_bap - timeout before
wlan0: prism2_tx - to BAP0 failed
wlan0: scheduled card reset
hostap_pci: wlan0: resetting card
wlan0: prism2_tx: hw not ready - skipping
wlan0: prism2_tx: hw not ready - skipping
prism2_hw_init: initialized in 220 ms
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: hfa384x_setup_bap - timeout after
wlan0: prism2_tx - to BAP0 failed
wlan0: scheduled card reset
hostap_pci: wlan0: resetting card
prism2_hw_init: initialized in 300 ms
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: prism2_tx: hw not ready - skipping
wlan0: prism2_tx: hw not ready - skipping
etc,etc....

We have tried to solve this problem by doubling the following timeouts in
prims_hw.c, but no success.

HFA384X_CMD_BUSY_TIMEOUT
HFA384X_BAP_BUSY_TIMEOUT

BUT when the firmware WEP is disabled or the WEP is done by hoastap driver
itself, all seems to work perfectly.

Is this a FW bug ? If we update the firmware 1.4.9 --> 1.5.6 does this
resolve our problem with firmware based WEP? Any ideas?

Best Regards, Jar