linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Piotr Findeisen <piotr.findeisen@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: unsupported TL-WN422G (0cf3:1006)
Date: Wed, 18 Nov 2009 00:44:43 +0100	[thread overview]
Message-ID: <200911180044.45287.s.L-H@gmx.de> (raw)
In-Reply-To: <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com>

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> 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

  parent reply	other threads:[~2009-11-17 23:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 16:21 unsupported TL-WN422G (0cf3:1006) Piotr Findeisen
2009-11-17 16:58 ` Stefan Lippers-Hollmann
2009-11-17 22:12   ` Piotr Findeisen
     [not found]   ` <ddb82bf60911171406r2c328f69ic3789f8e937e41f7@mail.gmail.com>
2009-11-17 23:44     ` Stefan Lippers-Hollmann [this message]
2009-11-18  7:58       ` Piotr Findeisen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911180044.45287.s.L-H@gmx.de \
    --to=s.l-h@gmx.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=piotr.findeisen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).