From: Peter Stuge <peter@stuge.se>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Performance problems with the AR9287
Date: Thu, 20 Oct 2011 04:30:47 +0200 [thread overview]
Message-ID: <20111020023047.31941.qmail@stuge.se> (raw)
In-Reply-To: <CABg7HFMyy5navZMCaLfZcD6ebOwsP1BX25QacUaLt0s-XbCWqQ@mail.gmail.com>
Mitch Davis wrote:
> > I disagree strongly. I would not at all expect that simply finding a
> > commit which exposes broken behavior will result in a fix.
..
> I thought so, and I agree. This particular problem could have been
> broken and fixed many times, and the odds of me finding the
> relevant one isn't good.
On the other hand, maybe the bisect is easy enough to do, and it
*might* be enough to identify the problem.
> > You basically have to find the problem on your own.
>
> Can you recommend a basic approach?
I'm afraid not. I'm also not an ath9k developer. If I would have the
same issues I expect I would spend a week or so on studying the
driver code and trying to reverse engineer the hardware.
> Are Adrian's comments about the entries in debugfs useful?
Yes!
> What should I be looking for?
I really don't know. Apparently the driver code quality is now good,
and there are no issues. I'm really happy that I haven't had to use
it for a while; issues that I might have run into together with sad
state of affairs on this mailing list would just make me too mad.
//Peter
next prev parent reply other threads:[~2011-10-20 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 22:26 [ath9k-devel] Performance problems with the AR9287 Mitch Davis
2011-10-20 0:15 ` Adrian Chadd
2011-10-20 0:15 ` Adrian Chadd
2011-10-20 2:02 ` Peter Stuge
2011-10-20 2:20 ` Mitch Davis
2011-10-20 2:30 ` Peter Stuge [this message]
2011-10-20 3:52 ` Adrian Chadd
2011-10-20 5:25 ` Ben Greear
2011-10-20 16:04 ` Mohammed Shafi
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=20111020023047.31941.qmail@stuge.se \
--to=peter@stuge.se \
--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.