Re: unsupported TL-WN422G (0cf3:1006)

[Piotr Findeisen <piotr.findeisen@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]

Hi, Stefan!

Thank you for all the help!

Unless i will be able to exchange my card with one based on zydas
chipset and if i will have some free time, I'll contact ath9_htc
developers (or the wiki) for any further reference and/or testing.

Funny think about this USB card is that, when I plugged it into my
laptop, it made my broken broadcom PCI-E card work again immediately, so
money was not lost completely :)

Best regards,
Piotr


On Wed, Nov 18, 2009 at 00:44, Stefan Lippers-Hollmann <s.L-H@gmx.de
<mailto:s.L-H@gmx.de>> wrote:
> Hi
>
> On Wednesday 18 November 2009, Piotr Findeisen wrote:
> > Hi, Stefan!
> > Thanks for your explanation!
> >
> > On Tue, Nov 17, 2009 at 17:58, Stefan Lippers-Hollmann <s.L-H@gmx.de
> <mailto:s.L-H@gmx.de>> wrote:
> >
> > > If you take a look at the vendor's windows driver for TP-LINK
> WN422G *v2*,
> >
> > how can I know I have v2 of the device?
> >
> > >  it becomes obvious that the device does not use the ZyDAS zd1211/
> Atheros
> > > 5007UG cipset, but has switched to the new Atheros AR9271 chipset
> (which
> > > technically is a 150 MBit/s 802.11n "lite" chipset family) instead.
> [...]
> > > %ATHER.DeviceDesc.1006% = ATHER_DEV_1006.ndi,    
> USB\VID_0CF3&PID_1006
>                                                              ^^^^     ^^^^
> Which means your device is TP-LINK WN422G v2 - and therefore AR9271.
>
> > OK, I found this section on the CD with the drivers but my product id is
> > 1006. How do you know it's AR9271 chipset and not, say, AR1006?
> > I found /AR9271/i on the CD in driver files for Windows 2000, XP, XP64.
> > Vista driver files don't have this substring anywhere (they have
> '9271' in
> > netathur.inf 6 times, and '1006' is 6 times in analogus lines as well).
> >
> > > At this moment a new driver called ath9k_htc is under (early)
> development:
> > >        http://wireless.kernel.org/en/users/Drivers/ath9k_htc
> >
> > What does 'early' mean in this context? Is it worth try or should i
> look for
> > replacement?
>
> Disclaimer, I neither have access to an AR9271 device, nor am familiar
> with
> its development state, therefore I base this on the afforementioned driver
> wiki page and the reference code.
>
> It's not merged in 2.6.32, wireless-next (~= 2.6.33) or wireless-testing
> yet and http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Status is
> pretty explicit about its state, namely that it doesn't actually transmit
> any data yet. Even though development seems to be pretty active and
> showing
> quite some potential, it will likely take several months before it becomes
> enduser compatible.
>
> Regards
>        Stefan Lippers-Hollmann




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]