Re: [zd1211-devs] Philips snu5600 usb dongle

2006-11-30 Thread Daniel Drake
unibrow wrote:
 Oh, and the reason I think it uses the AL2230_RF transmitter is because
 that's what dmesg | grep 'zd1211b\? chip' told me (zd1211rw 1-5:1.0:
 zd1211b chip 0471:1236 v4810 high 00-12-bf AL2230_RF pa0 g--, to be
 precise).

Thanks, added to my tree


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs


Re: [zd1211-devs] Philips snu5600 usb dongle

2006-11-29 Thread Uli Kunitz

Am 29.11.2006 um 11:54 schrieb unibrow:

 The thing is, I'm not really a coder (I dab a bit though) and I'm  
 certainly
 not familiar with driver code and other things related to kernel  
 code but I
 thought that since the WinXP driver is called ZD1211BU I'd take a  
 shot at
 adding the usb-id (0471:1236) to the zd_usb.c file of the driver and
 recompile. Now after recompilation the device is recognized (of  
 course) and
 the zd1211rw driver is loaded when the device is plugged. Fine and  
 dandy.
 However I only get 11 Mb/s reported by iwconfig even though it's a  
 802.11g
 device and I get 54 Mb/s in Windows. So I figure something is fishy  
 here and
 I would really like some help (and give help in return if I can)  
 from you
 guys.

Thank's for the USB id, I will add it to the driver.

I know this is a little bit disappointing, but the infrastructure we  
are using is
currently not supporting rate adaption. You can however use iwconfig  
to set
54 MBit/s manually.

# iwconfig eth1 rate 54M

 Oh, and the reason I think it uses the AL2230_RF transmitter is  
 because
 that's what dmesg | grep 'zd1211b\? chip' told me (zd1211rw  
 1-5:1.0:
 zd1211b chip 0471:1236 v4810 high 00-12-bf AL2230_RF pa0 g--, to be
 precise).

This is correct, because the RF is coded in the EEPROM of the device.  
You
wouldn't get an association with the AP, if the driver would identify  
the
wrong radio (RF chip).

Cheers,

Uli

--
Uli Kunitz




-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Zd1211-devs mailing list - http://zd1211.ath.cx/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs