Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Wiktor Zajas <w.zajas@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc compat-wireless tarballs should be up now
Date: Mon, 29 Mar 2010 21:40:09 +0200	[thread overview]
Message-ID: <20100329214009.804ec23f.wzajas@gmail.com> (raw)
In-Reply-To: <19376.15678.641255.41127@gargle.gargle.HOWL>

Thanks so much for this driver, it's working flawlessly. Only one minor problem was "Michael MIC failure detected", changing to AES helped.
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 ?

On Mon, 29 Mar 2010 11:10:14 +0530
Sujith <Sujith.Manoharan@atheros.com> wrote:

> mistah wrote:
> > I see just now about the firmware section on the README and I found from http://wireless.kernel.org/en/users/Drivers/ath9k_htc how to get it in here http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git . However I cant find the file ar9271.fw there and even if I find it, I would not know where to put it.
> 
> The firmware can be downloaded from:
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree
> 
> It has to be placed in /lib/firmware.
> I have updated the wiki, please check it.
> 
> Sujith
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel


-- 
Wiktor Zajas <wzajas@gmail.com>

  reply	other threads:[~2010-03-29 19:40 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 [this message]
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
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=20100329214009.804ec23f.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