From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] NF calibration and software level simulation of packet errors
Date: Tue, 15 Dec 2015 09:30:19 +0100 [thread overview]
Message-ID: <566FCF9B.30205@neratec.com> (raw)
In-Reply-To: <49310F74-314C-40AC-92EB-4CBDF35953E0@ieiit.cnr.it>
>
> Is this possible with ath9k? I cannot find any solution by myself. And
> the NOACK flag is not an option, since I am testing on rate adaptation
> techniques, so I need varying speeds and ACKs definitely.
You could use
REG_SET_BIT(ah, AR_DIAG_SW, AR_DIAG_ACK_DIS);
to disable or
REG_CLR_BIT(ah, AR_DIAG_SW, AR_DIAG_ACK_DIS);
to enable ACK's on per packet basis. I use it sometimes to verify retries.
>
> I have actually forced a periodic calibration, but I don?t know if it
> is the correct way of doing.
> Moreover, I discovered NF calibration takes nearly 20 ms. Can you
> confirm this? Is there a way to have a quicker behavior?
>
It takes more or less 20ms and it's dependent of numer of silent
periods and channel bandwidth. If you have constant noise then
driver will adapt to it an set a noise floor to that value. RSSI is will
be of course wrong on the absolute scale as it's always relative to NF.
Only way I know to speed it up is to calibrate NF on each
channel/bandwidth/temperature/environment for a specific card and use it
instead of
measured value. The problem is that CCA is not according to the
regulations as you don't really care what happens on the channel.
I hope it helps,
Wojtek
prev parent reply other threads:[~2015-12-15 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 13:52 [ath9k-devel] NF calibration and software level simulation of packet errors Federico Tramarin
2015-12-14 9:53 ` Federico Tramarin
2015-12-15 8:30 ` Wojciech Dubowik [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=566FCF9B.30205@neratec.com \
--to=wojciech.dubowik@neratec.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.