From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Question about ar9002_initvals.h file in ath9k driver
Date: Tue, 10 May 2011 19:49:07 -0700 [thread overview]
Message-ID: <4DC9F923.103@candelatech.com> (raw)
In-Reply-To: <20110511010818.29071.qmail@stuge.se>
On 05/10/2011 06:08 PM, Peter Stuge wrote:
> Mohammed Shafi wrote:
>> Adrian,
>> thanks a lot for the explanation. no one better explain more than this.
> Don't worry. From what I read Intel is doing worse. They communicate
> more, but with no significant content. They seem to have lots of
> serious problems.
Intel NICs can't do all the clever virtualization that Atheros
5k and 9k can, so what fun would they be anyway :)
>
> Another don't worry. I'm about to switch to a new computer. I'll get
> a shiny new AR9380 for it, and give ath9k another go on what must be
> a less broken PCI bus than the one in my current system.
The AR9380 NIC (sparklan 127N) I just started testing on 39-rc7-wl has been very
solid..once we fixed a few regressions that popped into the 39-wl
tree.
And, haven't seen any of those scary DMA splats either..I think Felix
and others must have finally squished that bug!
And, aside from one dodgy Ubiquity NIC, various other ath9k
cards have been working well too.
So, hopefully you'll start having better luck as well...
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-11 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 14:26 [ath9k-devel] Question about ar9002_initvals.h file in ath9k driver kang haiyang
2011-05-10 15:24 ` Adrian Chadd
2011-05-10 15:35 ` Mohammed Shafi
2011-05-11 0:44 ` kang haiyang
2011-05-11 1:08 ` Peter Stuge
2011-05-11 2:07 ` Adrian Chadd
2011-05-11 2:49 ` Ben Greear [this message]
2011-05-10 15:25 ` 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=4DC9F923.103@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.