From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Card AR928X very slow with new kernels
Date: Mon, 23 Apr 2012 07:50:31 -0700 [thread overview]
Message-ID: <4F956C37.8030108@candelatech.com> (raw)
In-Reply-To: <4F955D51.2020301@candelatech.com>
On 04/23/2012 06:46 AM, Ben Greear wrote:
> On 04/22/2012 11:58 PM, Mitch Davis wrote:
>> On Mon, Apr 23, 2012 at 1:07 PM, Ben Greear<greearb@candelatech.com> wrote:
>>>
>>> If you have a kernel that works, and one that doesn't, you can try to
>>> bisect and figure out what commit caused it to go bad.
>>>
>>> I must have deleted your first email..but can you be more specific
>>> about what kernel(s) work for you and which ones fail?
>>
>> That was Pierre, who started this thread.
>>
>> For me, I have two AR9287 cards in two almost identical laptops. For
>> one of them (wife's), the wireless has never worked well. The other
>> (mine) has been pretty good. Recently I swapped the wireless cards.
>> Mine started giving all sorts of trouble, but the wife's was no
>> better. When I upgraded from kernel 3.3.1 to 3.3.2, mine got a whole
>> lot better, whereas the wife's didn't. I suspect there are two problems,
>> one of which got fixed in 3.3.2.
Also, 3.3.1 had a bad ath9k regression, that was fixed in 3.3.2....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-04-23 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 0:54 [ath9k-devel] Card AR928X very slow with new kernels Pierre Willaime
2012-04-22 23:45 ` Mitch Davis
2012-04-23 1:39 ` Peter Stuge
2012-04-23 2:35 ` Mitch Davis
2012-04-23 3:07 ` Ben Greear
2012-04-23 3:16 ` Peter Stuge
2012-04-23 6:58 ` Mitch Davis
2012-04-23 12:47 ` Peter Stuge
2012-04-23 12:54 ` Mitch Davis
2012-04-23 13:46 ` Ben Greear
2012-04-23 14:50 ` 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=4F956C37.8030108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox