From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Wiktor Zajas <w.zajas@gmail.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now
Date: Tue, 20 Apr 2010 11:45:44 -0400 [thread overview]
Message-ID: <20100420154543.GA6472@tuxdriver.com> (raw)
In-Reply-To: <20100329222008.GA2852@tux>
On Mon, Mar 29, 2010 at 03:20:08PM -0700, Luis R. Rodriguez wrote:
> On Mon, Mar 29, 2010 at 12:40:09PM -0700, Wiktor Zajas wrote:
> > Thanks so much for this driver, it's working flawlessly. Only one minor problem
> > was "Michael MIC failure detected", changing to AES helped.
>
> Not sure if Sujith's patch posted yesterday would fix this.
>
> > I don't know if what I've done is correct, in order to recognize my card
> > (TL-WN422G v2) I've added "ATH9K_FW_USB_DEV(0x1006, "ar9271.fw")," to
> > "ath9k_hif_usb_ids[]", and changed "#define AR9271_USB 0x9271" to
> > "#define AR9271_USB 0x1006", is this the right thing to do ?
>
> Sort of, try this patch:
>
> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: [PATCH] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID
>
> Reported-by: Wiktor Zajas <w.zajas@gmail.com>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/hif_usb.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
> index fc4f6e8..a7664e4 100644
> --- a/drivers/net/wireless/ath/ath9k/hif_usb.c
> +++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
> @@ -21,6 +21,7 @@
>
> static struct usb_device_id ath9k_hif_usb_ids[] = {
> ATH9K_FW_USB_DEV(0x9271, "ar9271.fw"),
> + ATH9K_FW_USB_DEV(0x1006, "ar9271.fw"), /* TL-WN422G v2 */
> { },
> };
Any feedback on this?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-04-20 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43e72e891003281631i52f2800k23581c055fbc32ac@mail.gmail.com>
[not found] ` <43e72e891003281632x17f6d1d9i82640d96baa84096@mail.gmail.com>
[not found] ` <c13c21871003281831u74976d85lb3d4ece2d59c1f86@mail.gmail.com>
[not found] ` <43e72e891003281929hfff3821p65a9c42f15d9f6db@mail.gmail.com>
[not found] ` <c13c21871003281948y40edee0bi36c185b9dfaf4036@mail.gmail.com>
[not found] ` <43e72e891003282006l266141ehb78a2f4d46db76d6@mail.gmail.com>
[not found] ` <c13c21871003282118s80d7c8era5585af4a3377bc3@mail.gmail.com>
[not found] ` <c13c21871003282131x1ebaaee8h74f737c797b71b84@mail.gmail.com>
[not found] ` <19376.15678.641255.41127@gargle.gargle.HOWL>
[not found] ` <20100329214009.804ec23f.wzajas@gmail.com>
2010-03-29 22:20 ` [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now Luis R. Rodriguez
2010-04-20 15:45 ` John W. Linville [this message]
2010-04-20 17:36 ` Luis R. Rodriguez
2010-04-21 2:08 ` Sujith
2010-04-21 12:59 ` John W. Linville
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=20100420154543.GA6472@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=w.zajas@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).