Re: [zd1211-devs] Problem with new Abocom WUG2690

[Tom H. <TH...@er...>]

Please find below some additional information which may be useful.

I have enabled debug in the driver and get the following output when
I connect the module (Note the line "E2P_POD 0x0000000a" causing the
"UNKNOWN_A_RF"):

# usb 1-1.1: new full speed USB device using at91_ohci and address 3
usb 1-1.1: configuration #1 chosen from 1 choice
07b8:6001 v4810 full
usb 1-1.1: reset full speed USB device using at91_ohci and address 3
netdev->flags 0x1002
netdev->features 0x00000000
fw name zd1211/zd1211b_ub
Hotplug par1 = firmware action = add
loading /lib/firmware/zd1211/zd1211b_ub
firmware device id 0x4810 is equal to the actual device id
fw name zd1211/zd1211b_uphr
Hotplug par1 = firmware action = add
loading /lib/firmware/zd1211/zd1211b_uphr
transfer size 4096
transfer size 1024
firmware confirm return value 0x01

submit urb c7df1120

CR_AFTER_PNP 0x00000000
CR_GPI_EN 0x00000000
CR_INTERRUPT 0x00000000
fw_regs_base: 0xf7f1
E2P_POD 0x0000000a
RF UNKNOWN_A_RF 0xa PA type 0x0 patch CCK 0 patch CR157 0 patch 6M 0 new 
PHY 0 link LED2 tx led 1


CR_REG1: 0x00 -> 0x00
CR_REG1: 0x00 -> 0x80

aw 0 pt 0 bi 0
aw 0 pt 99 bi 100
CR_REG1: 0xa0 -> 0x20
value 0x025a000 bits 24
CR_REG1: 0x20 -> 0xa0
zd1211rw 1-1.1:1.0: firmware version 4725
FW_FIRMWARE_VER 0x4725
FW_USB_SPEED 0x0000
FW_FIX_TX_RATE 0x0000
FW_LINK_STATUS 0x0000
CR_AFTER_PNP 0x00000001
CR_GPI_EN 0x00000000
CR_INTERRUPT 0x00000000
zd1211rw 1-1.1:1.0: zd1211b chip 07b8:6001 v4810 full 00-12-0e 
UNKNOWN_A_RF pa0 -----
mac addr 00:12:0e:6b:5c:14
regdomain: 0x30
urb c7df1120 killed
successful
zd1211rw 1-1.1:1.0: eth1

Regards

Tom Hunter

zd1...@li... wrote on 25/06/2007 05:36:12 PM:

> 
> I am using the Abocom WUG2690 wireless USB module with Linux 2.6.21.
> 1 with the zd1211 driver from the latest 2.6.21.5. 
> 
> It appears that Abocom is using a mix of ZD1211 and ZD1211B chips 
> without assigning a different USB vendor/device-ID. The bulk of 
> devices I see use a ZD1211B. 
> 
> I have changed the "static struct usb_device_id usb_ids[]" table to 
> have the correct entry for a ZD1211B like this: 
> 
>         { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211B }, 
> 
> Unfortunately this means that it will no longer work with a ZD1211 
> (non-B variant). 
> 
> Another problem is that the AL2230S RF chip is not correctly 
> recognised, but seen as a "UNKNOWN_A_RF". I tried to work around 
> this by adding the type "UNKNOWN_A_RF" to the function 
> zd_rf_init_hw() in file zd_rf.c like this: 
> 
>         case UNKNOWN_A_RF: 
>         case AL2230_RF: 
>                 r = zd_rf_init_al2230(rf); 
> 
> This hack makes the driver work, but there is some packet loss. I 
> suspect that the RF chip is not setup correctly (for a AL2230S). 
> 
> Any ideas on how to fix this properly? 
> 
> Thanks 
> 
> Tom Hunter 



This email is confidential. If you are not the intended recipient you must 
not disclose or use the information contained in it. If you have received 
this email in error please notify us immediately by return email and 
delete this email and any attachments. ERG is not responsible for any 
changes made to this email or any attachments, other than those made by 
ERG, or for the effect of the changes on the meaning of the email or any 
attachments. ERG accepts no liability for any damage caused by this email 
or any attachments due to viruses, interference, interception, corruption 
or unauthorised access.