All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deep Shah <deep.shah@strixsystems.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9280 - OFDM RX errors?
Date: Mon, 24 Sep 2012 12:19:27 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120924T141830-698@post.gmane.org> (raw)
In-Reply-To: CAHOjGePBqtZPrn9JmrpFdGiBJga12iw=k6BArB32KLevDsKfjQ@mail.gmail.com

Deep Shah <deep.shah <at> strixsystems.com> writes:

> 
> Hi Adrian,Thank you very much for your reply. Madwifi versions
(madwifi-9.1.0.309 and madwifi-9.2.0.309) has support of
>  AR9300 in which the support is available for ar9390 chipset. I am using
madwifi-9.1.0.309  for my codebase. Regards,DeepOn Fri, Sep 21, 2012 at 3:03 AM,
Adrian Chadd <adrian <at> freebsd.org> wrote:
> 
> Hi,
> There's no AR9390 support in the madwifi codebase. Which driver
> codebase are you using?
> adrian
> On 20 September 2012 05:55, Deep Shah <deep.shah <at> strixsystems.com> wrote:
> > Adrian Chadd <adrian.chadd <at> gmail.com> writes:
> >
> >>
> >> On 8 February 2011 06:10, Adrian Chadd <adrian.chadd <at> gmail.com> wrote:
> >>
> >> > The throughput problems I'm having can be traced down (so far) to
> >> > -lots- of CCK/OFDM decoding errors. I get CRC errors and when I turned
> >> > on all the phy error mask bits, I also get various OFDM and CCK
> >> > decoding errors, with error 17 (OFDM timing) topping the lot.
> >>
> >> As a followup, I've just disabled ANI entirely and manually written in
> >> values to the sfcorr/sfcorr_low registers to disable OFDM weak
> >> detection. This significantly reduces the number of CRC/OFDM timing
> >> PHY errors when no traffic is going on, but there are still
> >> significant OFDM timing/CRC errors when RX'ing.
> >>
> >> What else should I look at?
> >>
> >> Adrian
> >>
> >


Hi,

The same was provided with the SDK of board which I am working on.

Also I want to understand that, 
any other functional change or some feature change (enable/disable) 
will be helpful in long distance link for better throughput?

Regards,
Deep

  reply	other threads:[~2012-09-24 12:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 22:10 [ath9k-devel] AR9280 - OFDM RX errors? Adrian Chadd
2011-02-08  2:51 ` Brian Prodoehl
2011-02-08  7:56   ` Adrian Chadd
2011-02-08 18:22     ` Luis R. Rodriguez
2011-02-08 19:01       ` Adrian Chadd
2011-02-09 17:33         ` Adrian Chadd
2011-02-08 13:15 ` Adrian Chadd
2012-09-20 12:55   ` Deep Shah
2012-09-20 21:33     ` Adrian Chadd
2012-09-21  6:28       ` Deep Shah
2012-09-24 12:19         ` Deep Shah [this message]
2012-09-21 11:33       ` Deep Shah
2012-09-22  8:30         ` Adrian Chadd
2012-09-24 12:16           ` Deep Shah
2012-09-24 18:19             ` Deep Shah
2012-09-25 15:34             ` Adrian Chadd

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=loom.20120924T141830-698@post.gmane.org \
    --to=deep.shah@strixsystems.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.