Hi Uli, Hi Daniel,

thanks for your quick answers.
Unfortunately I am not able ( dunno how ;) ) to set this flags in EEPROM and
so I have to wait until you guys might help me out. 

To show Daniel that my issue is not al2230s related, I patched the zd1211rw
files to the recent al2230s recognition (2.6.20 without any modifications).

Here are the two debug outputs

#-----------------------------------------------------------------------------
The first (serial number starts with 8131G3040...):

zd1211rw 1-1:1.0: zd_usb_enable_int()
zd1211rw 1-1:1.0: zd_usb_enable_int() submit urb c3cc53c0
zd1211rw 1-1:1.0: zd_chip_init_hw()
zd1211rw 1-1:1.0: dump_cr() CR_AFTER_PNP 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_GPI_EN 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_INTERRUPT 0x00000000
zd1211rw 1-1:1.0: zd_usb_init_hw() fw_base_offset: 0xf7f1
zd1211rw 1-1:1.0: read_pod() E2P_POD 0x80000104
zd1211rw 1-1:1.0: read_pod() RF AL2230_RF 0x4 PA type 0x0 patch CCK 1 patch
CR157 0 patch 6M 0 new PHY 1 link LED2 tx led 1
zd1211rw 1-1:1.0: hw_init()
zd1211rw 1-1:1.0: zd1211b_hw_reset_phy()
zd1211rw 1-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0x00 -> 0x00
zd1211rw 1-1:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x00 -> 0x80
zd1211rw 1-1:1.0: zd1211b_hw_init_hmac()
zd1211rw 1-1:1.0: get_aw_pt_bi() aw 0 pt 0 bi 0
zd1211rw 1-1:1.0: set_aw_pt_bi() aw 0 pt 99 bi 100
zd1211rw 1-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0xa0 -> 0x20
zd1211rw 1-1:1.0: zd_usb_rfwrite() value 0x025a000 bits 24
zd1211rw 1-1:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 -> 0xa0
zd1211rw 1-1:1.0: firmware version 4725
zd1211rw 1-1:1.0: dump_fw_registers() FW_FIRMWARE_VER 0x4725
zd1211rw 1-1:1.0: dump_fw_registers() FW_USB_SPEED 0x0000
zd1211rw 1-1:1.0: dump_fw_registers() FW_FIX_TX_RATE 0x0000
zd1211rw 1-1:1.0: dump_fw_registers() FW_LINK_STATUS 0x0000
zd1211rw 1-1:1.0: dump_cr() CR_AFTER_PNP 0x00000001
zd1211rw 1-1:1.0: dump_cr() CR_GPI_EN 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_INTERRUPT 0x00000000
zd1211rw 1-1:1.0: zd1211b chip 1582:6003 v4810 full 00-11-f6 AL2230_RF pa0
g--N-
zd1211rw 1-1:1.0: zd_write_mac_addr() mac addr 00:11:f6:7f:e6:ef
zd1211rw 1-1:1.0: zd_read_regdomain() regdomain: 0x30
zd1211rw 1-1:1.0: regdomain 0x30
zd1211rw 1-1:1.0: zd_usb_disable_int() urb c3cc53c0 killed
zd1211rw 1-1:1.0: probe() successful
zd1211rw 1-1:1.0: eth1

#-----------------------------------------------------------------------------
The second (serial number starts with 8131G3030...):

zd1211rw 1-1:1.0: zd_usb_enable_int()
zd1211rw 1-1:1.0: zd_usb_enable_int() submit urb c3cc51c0
zd1211rw 1-1:1.0: zd_chip_init_hw()
zd1211rw 1-1:1.0: dump_cr() CR_AFTER_PNP 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_GPI_EN 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_INTERRUPT 0x00000000
zd1211rw 1-1:1.0: zd_usb_init_hw() fw_base_offset: 0xf7f1
zd1211rw 1-1:1.0: read_pod() E2P_POD 0x00000004
zd1211rw 1-1:1.0: read_pod() RF AL2230_RF 0x4 PA type 0x0 patch CCK 0 patch
CR157 0 patch 6M 0 new PHY 0 link LED2 tx led 1
zd1211rw 1-1:1.0: hw_init()
zd1211rw 1-1:1.0: zd1211b_hw_reset_phy()
zd1211rw 1-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0x00 -> 0x00
zd1211rw 1-1:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x00 -> 0x80
zd1211rw 1-1:1.0: zd1211b_hw_init_hmac()
zd1211rw 1-1:1.0: get_aw_pt_bi() aw 0 pt 0 bi 0
zd1211rw 1-1:1.0: set_aw_pt_bi() aw 0 pt 99 bi 100
zd1211rw 1-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0xa0 -> 0x20
zd1211rw 1-1:1.0: zd_usb_rfwrite() value 0x025a000 bits 24
zd1211rw 1-1:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x20 -> 0xa0
zd1211rw 1-1:1.0: firmware version 4725
zd1211rw 1-1:1.0: dump_fw_registers() FW_FIRMWARE_VER 0x4725
zd1211rw 1-1:1.0: dump_fw_registers() FW_USB_SPEED 0x0000
zd1211rw 1-1:1.0: dump_fw_registers() FW_FIX_TX_RATE 0x0000
zd1211rw 1-1:1.0: dump_fw_registers() FW_LINK_STATUS 0x0000
zd1211rw 1-1:1.0: dump_cr() CR_AFTER_PNP 0x00000001
zd1211rw 1-1:1.0: dump_cr() CR_GPI_EN 0x00000000
zd1211rw 1-1:1.0: dump_cr() CR_INTERRUPT 0x00000000
zd1211rw 1-1:1.0: zd1211b chip 1582:6003 v4810 full 00-11-f6 AL2230_RF pa0
-----
zd1211rw 1-1:1.0: zd_write_mac_addr() mac addr 00:11:f6:80:91:6e
zd1211rw 1-1:1.0: zd_read_regdomain() regdomain: 0x30
zd1211rw 1-1:1.0: regdomain 0x30
zd1211rw 1-1:1.0: zd_usb_disable_int() urb c3cc51c0 killed
zd1211rw 1-1:1.0: probe() successful
zd1211rw 1-1:1.0: eth1

Hope this is somehow useful for doing some improvements.
Thank you.

Greetings from Berlin
Ulle



Ulrich Kunitz wrote:
> 
> Ulle,
> 
> I have here a 8183G3040... myself, it works quite reasonable  
> reflecting your experience. The G3030 seems not to have any patch  
> flags set in the EEPROM. We could however add a patch, which would  
> set the same flags as for G3040 if there aren't any flags set for a  
> 1582:6003 device.
> 
> If you don't want to do it on your own, you have to be a little bit  
> patient, because I'm a little bit short on time.
> 
> Uli
> 
> Am 12.05.2007 um 09:31 schrieb Ulle:
> 
>>
>> Hello,
>> I got two Longshine LCS-8131G3 sticks which have no obvious  
>> differences,
>> except a tiny one in dmesg:
>>
>> The first (serial number starts with 8131G3040...):
>> usb 1-1: new full speed USB device using uhci_hcd and address 23
>> usb 1-1: configuration #1 chosen from 1 choice
>> zd1211rw 1-1:1.0: firmware version 4725
>> zd1211rw 1-1:1.0: zd1211b chip 1582:6003 v4810 full 00-11-f6  
>> AL2230_RF pa0
>> g--N
>> zd1211rw 1-1:1.0: eth1
>>
>> The second (serial number starts with 8131G3030...):
>> usb 1-1: new full speed USB device using uhci_hcd and address 21
>> usb 1-1: configuration #1 chosen from 1 choice
>> zd1211rw 1-1:1.0: firmware version 4725
>> zd1211rw 1-1:1.0: zd1211b chip 1582:6003 v4810 full 00-11-f6  
>> AL2230_RF pa0
>> ----
>> zd1211rw 1-1:1.0: eth1
>>
>> Note the pa0 g--N and pa0 ---- .
>>
>> Does anybody know, what this means?
>> The second one I can not bring to inject packets, the first works  
>> okay with
>> injection.
>>
>> weird: I bought the second one half a year later then the first,  
>> but with
>> lower serial number :)
>>
>> How can those devices behave differently?
>>
>> Thanks for answers
>> Ulle
>>
>> P.S.: Sorry if posted twice.
>>
>> -- 
>> View this message in context: http://www.nabble.com/Different- 
>> hardware-versions-of-Longshine-LCS-8131G3-%281582%3A6003%29- 
>> tf3730927.html#a10443434
>> Sent from the zd1211-devs mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------- 
>> ---
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Zd1211-devs mailing list - http://zd1211.ath.cx/
>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
> 
> --
> Uli Kunitz
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Zd1211-devs mailing list - http://zd1211.ath.cx/
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Different-hardware-versions-of-Longshine-LCS-8131G3-%281582%3A6003%29-tf3730927.html#a10450687
Sent from the zd1211-devs mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to