All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT firmware beta-15 can now tune noise-floor thresholds.
Date: Tue, 1 Sep 2015 14:29:15 -0700	[thread overview]
Message-ID: <55E618AB.50902@candelatech.com> (raw)

Here is the changelog note.  This requires a corresponding driver patch to
enable configuring the firmware.  I tested this on my 4.0.4+ kernel.  I
will be adding this patch to my 3.17 and 4.2 (and future) kernels as well.

Should be useful for anyone trying (and failing) to pass ETSI CCA Adaptivity testing.

You are more likely to cause something to be worse than better, so don't use this
feature unless you know what you are doing and understand the consequences.

This firmware also has some debugging for a case where rate-ctrl gets stuck at
6Mbps and spews lots of dbglog messages into the logs.  This is not easy to
reproduce, but in case someone is debugging such an issue...please send me
full kernel logs if you detect the problem...maybe I can decode them and understand
the problem a bit better now.  You will need to be using my kernel (patches) in order to
get useful firmware logs, by the way.

   *  Enable setting noise-floor-threshold and min-cca-power.  If set, this will over
      ride the defaults, including eeprom (though firmware ignores these settings
      in the eeprom anyway.)  Don't mess with this unless you understand the
      consequences.  But, if set properly, noise-floor-threshold tweaking may fix
      ETSI CCA adapatibility test failures.


http://www.candelatech.com/ath10k.php


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: CT firmware beta-15 can now tune noise-floor thresholds.
Date: Tue, 1 Sep 2015 14:29:15 -0700	[thread overview]
Message-ID: <55E618AB.50902@candelatech.com> (raw)

Here is the changelog note.  This requires a corresponding driver patch to
enable configuring the firmware.  I tested this on my 4.0.4+ kernel.  I
will be adding this patch to my 3.17 and 4.2 (and future) kernels as well.

Should be useful for anyone trying (and failing) to pass ETSI CCA Adaptivity testing.

You are more likely to cause something to be worse than better, so don't use this
feature unless you know what you are doing and understand the consequences.

This firmware also has some debugging for a case where rate-ctrl gets stuck at
6Mbps and spews lots of dbglog messages into the logs.  This is not easy to
reproduce, but in case someone is debugging such an issue...please send me
full kernel logs if you detect the problem...maybe I can decode them and understand
the problem a bit better now.  You will need to be using my kernel (patches) in order to
get useful firmware logs, by the way.

   *  Enable setting noise-floor-threshold and min-cca-power.  If set, this will over
      ride the defaults, including eeprom (though firmware ignores these settings
      in the eeprom anyway.)  Don't mess with this unless you understand the
      consequences.  But, if set properly, noise-floor-threshold tweaking may fix
      ETSI CCA adapatibility test failures.


http://www.candelatech.com/ath10k.php


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2015-09-01 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 21:29 Ben Greear [this message]
2015-09-01 21:29 ` CT firmware beta-15 can now tune noise-floor thresholds Ben Greear

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=55E618AB.50902@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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.