From: Amith Belur <amithbn@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Help needed to identify if the device works with ath9k
Date: Sat, 7 Jul 2012 13:56:21 +0200 [thread overview]
Message-ID: <CADxMoMdPsfDOSO68cAHUgOe0Uvs+=_uXfNwEyTbWo_q6t0TZzg@mail.gmail.com> (raw)
In-Reply-To: <CAD2nsn3oLOpw6bpPbQgud9J4Ck=XUFJzRjC03AM7_6mZtepw1g@mail.gmail.com>
Thank you for the response. The wireless device has 2 chips. AR9170 is
listed under Carl9170-supported devices and AR9102 is listed under
ath9k. However, AR9170 is the chip that talks to the software. Hence,
the device is not supported by ath9k.
http://www.wikidevi.com/files/Atheros/specsheets/AR9001U.pdf
On Wed, Jul 4, 2012 at 4:03 PM, Mohammed Shafi <shafi.wireless@gmail.com> wrote:
> On Mon, Jul 2, 2012 at 10:36 PM, Amith Belur <amithbn@gmail.com> wrote:
>> I am using TP LINK TL-WN822N wireless device which has two chips. It works
>> with Carl9170, however I would like to use ath9k which according to the site
>> supports AR9102 which is one of the chips. I tried disabling Carl9170 driver
>> my NIC was using and loading ath9k using modprobe. However, the device is
>> not enabled with ath9k. Any pointers what needs to be done?
>
> ath9k_htc supported devices
> http://linuxwireless.org/en/users/Drivers/ath9k_htc/#Supported_Devices
>
>>
>> --
>> Best Regards,
>> Amith
>>
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
>
> --
> thanks,
> shafi
--
Best Regards,
Amith
prev parent reply other threads:[~2012-07-07 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 17:06 [ath9k-devel] Help needed to identify if the device works with ath9k Amith Belur
2012-07-04 14:03 ` Mohammed Shafi
2012-07-07 11:56 ` Amith Belur [this message]
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='CADxMoMdPsfDOSO68cAHUgOe0Uvs+=_uXfNwEyTbWo_q6t0TZzg@mail.gmail.com' \
--to=amithbn@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
/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).