From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Spectral Scan
Date: Thu, 24 Jul 2014 16:11:13 -0700 [thread overview]
Message-ID: <CAJ-Vmonc6JEaire3s9e4zcprUGPArdXm9h3=n+xAuP6qt_QHRQ@mail.gmail.com> (raw)
In-Reply-To: <CAMhWHyY12-PuQnTuBjkX_dsxjZ=PJQ4LxoGhX9FPKce-U6=kaQ@mail.gmail.com>
Hi,
The NIC is either receiving frames or doing spectral scan. It can't
unfortunately do both.
-a
On 23 July 2014 13:34, mahaveer gupta <mgupta1616@gmail.com> wrote:
> Thanks for the answer. Indeed, we thought similar to what you suggest but
> realized that the actual packets still need to be decoded to be able to
> match the spectral samples with decoded packets (by matching the hardware
> timestamp values). Hence this was a little tricky.
>
> If we use a 40Mhz scan on a 20MHz transmission, how would it be possible to
> distinguish the spectral samples corresponding to 20MHz packets and those
> corresponding to background noise.
>
> RSSI could be a weak discriminator.
>
>
> On Wed, Jul 23, 2014 at 2:50 PM, Kamran Nishat <kamran.nishat@gmail.com>
> wrote:
>>
>> hi
>> yes this is the expected behaviour. one can only get spectral scans for
>> things cannot be decoded as valid packets by HW. One way to receive scans
>> for packets is to scan on 40MHz channel while sending traffic on a 20Mhz
>> sub channel.
>>
>> kamran
>>
>>
>> On Thu, Jul 24, 2014 at 12:29 AM, mahaveer gupta <mgupta1616@gmail.com>
>> wrote:
>>>
>>> Hello,
>>>
>>> We have been able to use the spectral scan feature successfully -
>>> http://wireless.kernel.org/en/users/Drivers/ath9k/spectral_scan
>>>
>>> However, samples are being skipped while the device is receiving packets.
>>> The spectral samples we see correspond to background noise while no packet
>>> is being received.
>>>
>>> Wondering if this behavior is expected and if yes, kindly let me know if
>>> you have a suggestion to change that. We would like to see the spectral
>>> samples corresponding to successfully decoded packets. We tried all three
>>> modes without any success so far.
>>>
>>> We are using AR 9271 Chipset with the usual firmware.
>>>
>>> --
>>> Thanks,
>>> M
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>
>
>
>
> --
> Thanks,
> M
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
next prev parent reply other threads:[~2014-07-24 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 19:29 [ath9k-devel] Spectral Scan mahaveer gupta
2014-07-23 19:50 ` Kamran Nishat
2014-07-23 20:34 ` mahaveer gupta
2014-07-24 23:11 ` Adrian Chadd [this message]
2016-11-07 11:34 [ath9k-devel] spectral scan Simone Di Domenico
2016-11-10 0:28 ` 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='CAJ-Vmonc6JEaire3s9e4zcprUGPArdXm9h3=n+xAuP6qt_QHRQ@mail.gmail.com' \
--to=adrian@freebsd.org \
--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;
as well as URLs for NNTP newsgroup(s).