Hi,
Thanks for this great piece of work! I recently got a "Siemens Gigaset USB
Adapter 108" and it works with this driver.
I had to make a small change to the USB device id, so it was detected.
There's something strange with this adapter. Without the driver, lsusb
identifies it as:
"Bus 001 Device 004: ID 129b:160c CyberTAN Technology". If I put 160c into
ar5523.c, the driver loads automagically when plugging in the adapter, but
there will be an initialization timeout, and the device can't initialize.
After the driver is loaded, lsusb identifies it as:
"Bus 001 Device 006: ID 129b:160b CyberTAN Technology". Everything works
fine if I put 160b into ar5523.c . I guess this must be somekind of
harware bug/feature, because something similar happened using ndiswrapper
(couldn't get that working anyway). There also is an "160d" around
according to Google. I guess these are all slight variations of the same
piece of hardware, and all are reported to work with this driver, so I
would suggest to replace the add-Gigaset-108.patch into this, to cover
them all:
--- a/ar5523.c
+++ b/ar5523.c
@@ -1623,6 +1623,9 @@ static struct usb_device_id ar5523_id_ta
AR5523_DEVICE_UX(0x0cf3, 0x0005), /* Atheros2 / AR5523_3 */
AR5523_DEVICE_UG(0x0d8e, 0x7801), /* Conceptronic / AR5523_1 */
AR5523_DEVICE_UX(0x0d8e, 0x7811), /* Conceptronic / AR5523_2 */
+ AR5523_DEVICE_UG(0x129b, 0x160b), /* Cybertan / GIGASET108_1 */
+ AR5523_DEVICE_UG(0x129b, 0x160c), /* Cybertan / GIGASET108_2 */
+ AR5523_DEVICE_UG(0x129b, 0x160d), /* Cybertan / GIGASET108_3 */
AR5523_DEVICE_UX(0x2001, 0x3a00), /* Dlink / DWLAG132 */
AR5523_DEVICE_UG(0x2001, 0x3a02), /* Dlink / DWLG132 */
AR5523_DEVICE_UX(0x2001, 0x3a04), /* Dlink / DWLAG122 */
Kind regards,
--
[alwin]
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
