From: Peizhao Hu <peizhao.research@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Spectral Scan in ath9k
Date: Fri, 01 Jun 2012 13:01:11 +1000 [thread overview]
Message-ID: <4FC83077.6010607@gmail.com> (raw)
In-Reply-To: <CAJ-VmomF1V7R3nUUs0fyDrgnbzptHw9EOtHXVONe6g3sxV-BgQ@mail.gmail.com>
On 01/06/12 05:19, Adrian Chadd wrote:
> Argh, there's more to it.. :-)
>
> For AR9160 and later, you can enable the FFT bit in one of the radar
> registers and you'll get some FFT reports for longer radar pulses.
> It's enabled by default in the code that we've committed to ath9k and
> FreeBSD HAL.
>
> Spectral scan mode is related but different (and not in AR9160.)
>
> So for longer pulses, you'll get RADAR payload (phyerr code = 5) which
> may just have the pri/ext pulse duration and some config info, or it
> may have a series of FFT reports first. That's just for radar stuff
> though, it's not spectral scan.
>
> That's why he mentioned code = 5 or code = 38.
>
>
> Adrian
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Hi Adrian,
To summarize what you saying if I have later chipset than AR9160 (e.g.,
AR9280/AR9285), then the FFT bit is enabled by default.
So for longer pulses, you'll get RADAR payload (phyerr code = 5) which
may just have the pri/ext pulse duration and some config info, or it
may have a series of FFT reports first. That's just for radar stuff
though, it's not spectral scan.
Could you please explain what you mean by the radar stuff? So what is
the spectral scan report? does anyone know?
Is there anyone ready to start a documentation on this feature?
--
Regards;
Peizhao
next prev parent reply other threads:[~2012-06-01 3:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 15:50 [ath9k-devel] Spectral Scan in ath9k Saulo Queiroz
2012-03-24 22:53 ` Adrian Chadd
2012-05-30 10:25 ` Alex Hacker
2012-05-31 10:58 ` Saulo Queiroz
2012-05-31 13:27 ` Alex Hacker
2012-05-31 14:48 ` abhinav narain
2012-05-31 19:19 ` Adrian Chadd
2012-06-01 3:01 ` Peizhao Hu [this message]
2012-06-01 14:10 ` Adrian Chadd
2012-06-01 8:57 ` Alex Hacker
2013-05-08 16:15 ` Claudio
2013-05-08 17:50 ` Oleksij Rempel
2013-06-10 15:15 ` Gui Iribarren
2013-07-25 13:43 ` [ath9k-devel] Realtime plot of " Gui Iribarren
2013-07-25 19:54 ` Adrian Chadd
2013-07-26 16:18 ` Gui Iribarren
2013-07-26 18:26 ` Gui Iribarren
2013-07-26 21:18 ` Adrian Chadd
2013-07-28 7:29 ` Gui Iribarren
2013-07-28 17:52 ` Adrian Chadd
2013-07-30 12:12 ` Michal Kazior
2013-07-25 20:24 ` [ath9k-devel] Measurements with " Gabriel Tolón
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=4FC83077.6010607@gmail.com \
--to=peizhao.research@gmail.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.