From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k for ar9102 and ar9103, OpenWRT, AP81 router hardware
Date: Wed, 17 Dec 2008 02:57:00 -0800 [thread overview]
Message-ID: <20081217105700.GE14261@tesla> (raw)
In-Reply-To: <eef88e5b0812171053j35336196j15dbaf7f63ee9ae5@mail.gmail.com>
On Wed, Dec 17, 2008 at 10:53:46AM -0800, Stephen Gutknecht (hilltx) wrote:
> Howdy,
>
> First off, I am not a OpenWRT developer, just a participatory user.
> However, I'm hoping someone here is also an openwrt user and we can
> trade source files that I can test on the router hardware and pass
> results back on to the OpenWRT developers.
>
> I am on the latest development release of OpenWRT; but the included
> madwifi nor ath9k driver works on these ar9102 or ar9103 adapters.
> not in client mode, not at all.
>
> First off, do newer updates to ath9k possibly support these chips?
> Then I can try to update my OpenWRT with the newer source files.
>
> If no drivers exist for the ar9102, can they be adapted? just a
> matter of a new pci hardware ID or is this a major change?
>
> Any help and tips appreciated. I started a new thread over on the
> OpenWRT forum:
> http://forum.openwrt.org/viewtopic.php?id=18113
What is an AR9102 or AR9103? Please see:
http://wireless.kernel.org/en/users/Drivers/ath9k#supportedchipsets
Luis
next prev parent reply other threads:[~2008-12-17 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 18:53 [ath9k-devel] ath9k for ar9102 and ar9103, OpenWRT, AP81 router hardware Stephen Gutknecht
2008-12-17 10:57 ` Luis R. Rodriguez [this message]
2008-12-27 23:45 ` Stephen Gutknecht
2008-12-28 21:55 ` Pavel Roskin
2008-12-28 22:22 ` Stephen Gutknecht
2008-12-29 16:07 ` Luis R. Rodriguez
2008-12-29 16:24 ` Stephen Gutknecht
2008-12-29 18:05 ` Luis R. Rodriguez
2008-12-29 19:17 ` Stephen Gutknecht
2008-12-29 19:47 ` Luis R. Rodriguez
2008-12-29 22:34 ` RHS Linux User
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=20081217105700.GE14261@tesla \
--to=lrodriguez@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.