From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ar9003_rxs struct
Date: Sun, 8 May 2016 22:33:16 -0700 [thread overview]
Message-ID: <CAJ-Vmond9Y5ooSMrY0V0DnQ4vYw70qrY5hQ9AbtAHJGg6LxJ_Q@mail.gmail.com> (raw)
In-Reply-To: <loom.20160509T035512-483@post.gmane.org>
i think for the later hardware there's some way to get it as part of
the normal payload, because I /think/ that's how the wifi positioning
stuff gets fine resolution information.
I should really dig it all up.
-adrian
On 8 May 2016 at 19:01, Allen Welkie <allen.welkie@gmail.com> wrote:
> Adrian Chadd <adrian <at> freebsd.org> writes:
>
>>
>> Hi,
>>
>> It's just a placeholder for each of the fields defined. look at
>> ath9k_hw_process_rxdesc_edma() for what those fields mean.
>>
>> -a
>>
>
> The author of the "Atheros CSI tool" found that there is CSI data just past
> this struct on some of the received frames (in the `buf_addr` buffer passed
> to the `ath9k_hw_process_rxdesc_edma' function). The author claims that they
> experimentally found the CSI data:
>
> https://github.com/xieyaxiongfly/Atheros-CSI-Tool/issues/4
>
> Is this behavior documented anywhere (other than in the source code)? Is
> there any way we know for sure which frames contain CSI data?
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
prev parent reply other threads:[~2016-05-09 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 15:24 [ath9k-devel] ar9003_rxs struct Dan
2016-04-13 18:57 ` Adrian Chadd
2016-05-09 2:01 ` Allen Welkie
2016-05-09 5:33 ` Adrian Chadd [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=CAJ-Vmond9Y5ooSMrY0V0DnQ4vYw70qrY5hQ9AbtAHJGg6LxJ_Q@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 read-only IMAP folder(s) and NNTP newsgroup(s).