From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Extensive AR9280 Documentation
Date: Thu, 06 Jan 2011 15:19:02 -0800 [thread overview]
Message-ID: <4D264DE6.20900@candelatech.com> (raw)
In-Reply-To: <AANLkTimRZrJ6kZUW+rMSU8yBXevFpcUp9gJ+8pO6L36Z@mail.gmail.com>
On 01/06/2011 03:14 PM, Luis R. Rodriguez wrote:
> On Thu, Jan 6, 2011 at 3:04 PM, Ben Greear<greearb@candelatech.com> wrote:
>> On 01/06/2011 02:17 PM, Luis R. Rodriguez wrote:
>>
>>> so it takes time. In the meantime we do enable active developers to
>>> work with engineers through our private internal list but since
>>> ath9k is Actively maintained by Atheros engineers if you have issues
>>> they should be clearly reported and Atheros will take care of them.
>>
>> I'd love it if some of those active developers would ack/nack some
>> patches I've posted recently. I'm attempting to track down some
>> issue with tx queues being stopped and not sending pkts to
>> the hardware, and instrumenting debugfs as I've been doing
>> seems a good way to debug it. If I can get those patches in,
>> I can better report the way I'm causing the problem and maybe you can
>> reproduce it...
>
> Sure, it was the holidays you know, I just got back in to SF
> yesterday, for example.
Glad to have you back! Debugging ath9k is quite lonely
by oneself :P
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-01-06 23:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 18:39 [ath9k-devel] Extensive AR9280 Documentation Galen
2011-01-06 19:37 ` Daniel Halperin
2011-01-06 20:01 ` Peter Stuge
2011-01-06 20:57 ` Daniel Halperin
2011-01-06 21:20 ` Luis R. Rodriguez
2011-01-06 21:45 ` Peter Stuge
2011-01-06 22:17 ` Luis R. Rodriguez
2011-01-06 23:04 ` Ben Greear
2011-01-06 23:14 ` Luis R. Rodriguez
2011-01-06 23:19 ` Ben Greear [this message]
2011-01-06 23:22 ` Luis R. Rodriguez
2011-01-06 23:31 ` Ben Greear
2011-01-07 8:49 ` Adrian Chadd
2011-01-08 11:30 ` Luca Olivetti
2011-01-06 21:33 ` Peter Stuge
2011-01-06 22:22 ` Luis R. Rodriguez
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=4D264DE6.20900@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.