From: Wiktor Zajas <w.zajas@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now
Date: Tue, 30 Mar 2010 17:32:08 +0200 [thread overview]
Message-ID: <20100330173208.f52e72c7.wzajas@gmail.com> (raw)
In-Reply-To: <20100329222008.GA2852@tux>
I applied it, and I've also added this patch http://marc.info/?l=linux-wireless&m=126985782708016&w=4, but it's not enough. I still need to have #define AR9271_USB 0x1006 in hw.h.
On Mon, 29 Mar 2010 15:20:08 -0700
"Luis R. Rodriguez" <lrodriguez@atheros.com> 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 */
> { },
> };
>
> --
> 1.6.3.3
>
>
> ********************************************************************************
> Git Achievement Unlocked!
>
> Apprentice Archivist (Level 3)
> Prepare each commit with its patch in one file per commit with git format-patch
> ********************************************************************************
>
--
Wiktor Zajas <wzajas@gmail.com>
next prev parent reply other threads:[~2010-03-30 15:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 2:43 [ath9k-devel] ath9k_htc compat-wireless tarballs should be up now Luis R. Rodriguez
2010-03-28 17:39 ` mistah
2010-03-28 18:13 ` mistah
2010-03-28 23:31 ` Luis R. Rodriguez
2010-03-28 23:32 ` Luis R. Rodriguez
2010-03-29 1:31 ` mistah
2010-03-29 2:29 ` Luis R. Rodriguez
2010-03-29 2:36 ` Yongheng Qi
2010-03-29 2:38 ` Luis R. Rodriguez
2010-03-29 2:40 ` Yongheng Qi
2010-03-29 2:48 ` mistah
2010-03-29 3:06 ` Luis R. Rodriguez
2010-03-29 4:18 ` mistah
2010-03-29 4:31 ` mistah
2010-03-29 5:40 ` Sujith
2010-03-29 19:40 ` Wiktor Zajas
2010-03-29 22:20 ` [ath9k-devel] ath9k_htc: add the 0cf3:1006 TL-WN422G v2 device ID now Luis R. Rodriguez
2010-03-30 15:32 ` Wiktor Zajas [this message]
2010-04-20 15:45 ` John W. Linville
2010-04-20 17:36 ` Luis R. Rodriguez
2010-04-21 2:08 ` Sujith
2010-04-21 12:59 ` John W. Linville
2010-03-30 3:47 ` [ath9k-devel] ath9k_htc compat-wireless tarballs should be up now Sujith
2010-03-30 15:00 ` Dyno Fu
2010-03-31 11:16 ` Sujith
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=20100330173208.f52e72c7.wzajas@gmail.com \
--to=w.zajas@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