On Tuesday 15 September 2009 13:37:13 Stefan Lippers-Hollmann wrote: > On Tuesday 15 September 2009, Christian Lamparter wrote: > > On Tuesday 15 September 2009 07:52:19 Fabian Lenz wrote: > > > Here the output of lsusb: > > > > > > Bus 002 Device 003: ID 0cf3:1002 Atheros Communications, Inc. > > > > they made two revisions (v1 and v2). > > Do you know which one you've got? > > v1 (FCC ID: TE7WN821NV1) at least identifies itself as: > ID 0cf3:9170 Atheros Communications, Inc. AR9170 802.11n thanks! so, they sticked with the correct id for v1. > > > and the product page of the WLAN stick: > > > > > > http://www.tp-link.com/products/product_des.asp?id=140 > > > > > > I added { USB_DEVICE(0x0cf3, 0x1002) } to the usb.c file manually some time > > > ago and got my stick to work but the connection is somewhat unstable... but > > > that's another story. > > what firmware image do you use? > > the two-stage (ar9170-1.fw & ar9170-2.fw) firmware should work. > > for one-stage you should use a bleeding edge wireless-testing tree. > > On this TL-WN821N v1 the one-stage (as published in binary from by Atheros, > so far I had problems with my self compiled one) and two-stage firmwares > work equally well on a vanilla 2.6.31 kernel: the catch here is that some devices won't work with the two-stage firmware (e.g: AVM FRITZ!WLAN USB Stick N 2.4 ) That's why the delay. Regards, Chr -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
