From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath9k-devel@lists.ath9k.org, rodrigue@qca.qualcomm.com,
nbd@openwrt.org, jonbither@gmail.com, kgiori@qca.qualcomm.com,
mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [RFCv2] Add spectral scan support for Atheros AR92xx/AR93xx
Date: Mon, 31 Dec 2012 09:46:39 +0100 [thread overview]
Message-ID: <20121231084639.GB23038@pandem0nium> (raw)
In-Reply-To: <CAJ-VmonRjawqBY+F_-in3sSTpen=KaW9FNrG=140q38NtFCJbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
Hey Adrian,
On Sun, Dec 30, 2012 at 09:33:06PM -0800, Adrian Chadd wrote:
> Hi,
>
> I'm just going through and hacking on this now for FreeBSD (and
> userland decoding, rather than kernel side decoding.)
Cool!
>
> Your frame length logic is OK for the short spectral scan reports, but
> not useful for the longer aggregate reports (short_rpt=0 IIRC.)
Yeah, I've always used short_rpt=1 AFAIR.
>
> Here there's >1 FFT report in a frame, _and_ it could be corrupted,
> _and_ it could be short.
That sounds like a lot of fun :P
>
> I'm just writing a userland library now to start parsing and
> correcting these. It's likely that I can use your logic for the short
> spectral reports, but I won't be able to use them for the longer
> aggregate reports. We'll need to find some other way to determine that
> they've been corrupted and just toss/correct as appropriate.
>
> Thanks for digging into this!
Before asking questions, I'll wait for your userland lib and see what
it does. I've seen some longer frames as well occasionally when starting
to play with spectral, but didn't care too much as I didn't know how to
handle it. Anyway, I prefer hiding the corrupt and messy part and only
pass "clean data" to userspace, at least with the Linux implementation.
If you have some code handling and/or correct these long dataframes, I'd
be happy to integrate it if possible.
Thanks!
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-12-31 8:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 16:36 [RFCv2] Add spectral scan support for Atheros AR92xx/AR93xx Simon Wunderlich
2012-12-06 16:36 ` [RFCv2] ath9k: add spectral scan feature Simon Wunderlich
2012-12-13 14:07 ` [RFCv2] Add spectral scan support for Atheros AR92xx/AR93xx Simon Wunderlich
2012-12-13 17:25 ` Felix Fietkau
2012-12-13 22:06 ` Simon Wunderlich
2012-12-13 23:04 ` Felix Fietkau
2012-12-14 0:24 ` Tobias Steinicke
2012-12-14 0:30 ` Adrian Chadd
2012-12-16 3:48 ` Adrian Chadd
2012-12-16 4:06 ` Adrian Chadd
2012-12-17 13:22 ` Simon Wunderlich
2012-12-17 18:48 ` Adrian Chadd
2012-12-18 11:08 ` Zefir Kurtisi
2012-12-18 13:46 ` Simon Wunderlich
2012-12-18 16:02 ` Zefir Kurtisi
2012-12-28 3:11 ` Adrian Chadd
2012-12-31 5:33 ` Adrian Chadd
2012-12-31 8:46 ` Simon Wunderlich [this message]
2012-12-31 14:38 ` Adrian Chadd
2012-12-31 7:48 ` Adrian Chadd
2012-12-31 8:40 ` Simon Wunderlich
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=20121231084639.GB23038@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=jonbither@gmail.com \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=nbd@openwrt.org \
--cc=rodrigue@qca.qualcomm.com \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=zefir.kurtisi@neratec.com \
/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