[ath9k-devel] ar9003_rxs struct
Adrian Chadd <[email protected]>
| Newsgroups | org.ath9k.lists.ath9k-devel |
|---|---|
| Message-ID | <CAJ-Vmond9Y5ooSMrY0V0DnQ4vYw70qrY5hQ9AbtAHJGg6LxJ_Q@mail.gmail.com> |
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 <[email protected]> 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