From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Stable Version for ath9k_htc in AP Mode?
Date: Wed, 30 Apr 2014 21:12:27 -0700 [thread overview]
Message-ID: <5361C9AB.5060402@candelatech.com> (raw)
In-Reply-To: <CAFjWW+ZT27sKm9s=9DQiTa_95q_oUep7OAgcZGew8UMcv7jqVw@mail.gmail.com>
On 04/30/2014 11:59 AM, Aaron Hamilton wrote:
> Unfortunately our units are in another state, so we're unable to make
> the electrical connections. If the UART is RS-232, we might be able to
> modify some locally - but it'll be a rather difficult challenge. Not
> to mention, we see a great deal of issues in the field, but can't
> duplicate them here.
>
> On the firmware, I'm pulling down io_clean-2014.04.29 right now. I'm
> assuming this is what I should be using?
>
> Are there any other options for debugging aside from the UART? We're
> really in a bind and feel like the only work around is to setup a task
> to restart hostapd every hour.
Can you use a 'real' ath9k NIC that doesn't use firmware?
I think any time you can get rid of the firmware layer you
are likely to get a much better result...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-05-01 4:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 20:43 [ath9k-devel] Stable Version for ath9k_htc in AP Mode? Aaron Hamilton
2014-04-28 22:03 ` Oleksij Rempel
2014-04-29 6:19 ` Aaron Hamilton
2014-04-29 6:31 ` Oleksij Rempel
2014-04-29 9:08 ` Aaron Hamilton
2014-04-30 17:29 ` Aaron Hamilton
2014-04-30 18:27 ` Oleksij Rempel
2014-04-30 18:59 ` Aaron Hamilton
2014-04-30 20:16 ` Oleksij Rempel
2014-04-30 20:40 ` Oleksij Rempel
2014-04-30 23:03 ` Aaron Hamilton
2014-05-01 5:37 ` Oleksij Rempel
2014-05-01 21:33 ` Aaron Hamilton
2014-05-01 22:00 ` Aaron Hamilton
2014-05-01 22:41 ` Oleksij Rempel
2014-05-02 6:27 ` Aaron Hamilton
2014-05-02 10:11 ` Aaron Hamilton
2014-05-03 9:07 ` Oleksij Rempel
2014-05-05 18:09 ` Aaron Hamilton
2014-05-05 19:32 ` Oleksij Rempel
2014-05-06 1:57 ` Aaron Hamilton
2014-05-06 7:21 ` Oleksij Rempel
2014-05-08 22:57 ` Aaron Hamilton
2014-05-10 9:26 ` Oleksij Rempel
2014-05-11 6:40 ` Aaron Hamilton
2014-05-11 15:40 ` Adrian Chadd
2014-05-12 1:46 ` Aaron Hamilton
2014-05-12 8:01 ` Oleksij Rempel
2014-05-12 13:11 ` Peter Stuge
2014-05-12 14:47 ` Oleksij Rempel
2014-05-28 5:36 ` Aaron Hamilton
2014-05-30 4:21 ` Oleksij Rempel
2014-06-04 18:06 ` Aaron Hamilton
2014-06-06 2:12 ` Aaron Hamilton
2014-06-06 7:52 ` Oleksij Rempel
2014-06-06 11:06 ` Aaron Hamilton
2014-06-06 20:24 ` Gui Iribarren
2014-06-06 20:27 ` Gui Iribarren
2014-05-01 4:12 ` Ben Greear [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=5361C9AB.5060402@candelatech.com \
--to=greearb@candelatech.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.