All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 00/11] ath9k: Spectral scan updates
Date: Fri, 1 May 2015 08:46:22 -0400	[thread overview]
Message-ID: <20150501124622.GD14037@localhost> (raw)
In-Reply-To: <1430351482-59418-1-git-send-email-mickflemm@gmail.com>

On Wed, Apr 29, 2015 at 11:51:11PM +0000, Nick Kossifidis wrote:
> Now we need someone to write a nice real-time GUI for that...

This fails on the "nice" front, but as a starting point for something
"real-time" I hacked up this thing a while ago (most of the existing
tools I found for this were offline post-processors):

https://github.com/bcopeland/speccy

The visualization is basically garbage so complete rewrites welcome :)

I'll give your patches on my ath9k_htc device.

-- 
Bob Copeland %% http://bobcopeland.com/

WARNING: multiple messages have this Message-ID (diff)
From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: kvalo@codeaurora.org, ath9k-devel@qca.qualcomm.com,
	linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	adrian.chadd@gmail.com
Subject: Re: [PATCH 00/11] ath9k: Spectral scan updates
Date: Fri, 1 May 2015 08:46:22 -0400	[thread overview]
Message-ID: <20150501124622.GD14037@localhost> (raw)
In-Reply-To: <1430351482-59418-1-git-send-email-mickflemm@gmail.com>

On Wed, Apr 29, 2015 at 11:51:11PM +0000, Nick Kossifidis wrote:
> Now we need someone to write a nice real-time GUI for that...

This fails on the "nice" front, but as a starting point for something
"real-time" I hacked up this thing a while ago (most of the existing
tools I found for this were offline post-processors):

https://github.com/bcopeland/speccy

The visualization is basically garbage so complete rewrites welcome :)

I'll give your patches on my ath9k_htc device.

-- 
Bob Copeland %% http://bobcopeland.com/

  parent reply	other threads:[~2015-05-01 12:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 23:51 [ath9k-devel] [PATCH 00/11] ath9k: Spectral scan updates Nick Kossifidis
2015-04-29 23:51 ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 01/11] ath9k: Add a new debug flag for FFT spectral scan Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-05-09 13:47   ` [ath9k-devel] [01/11] " Kalle Valo
2015-05-09 13:47     ` Kalle Valo
2015-04-29 23:51 ` [ath9k-devel] [PATCH 02/11] ath9k: Fix hanlding of maximum magnitude index Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 03/11] ath9k: Move processing of FFT frames to different functions Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 04/11] ath9k: Perform integrity checks when processing FFT frames Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 05/11] ath9k: Support processing of multiple FFT frames per report Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 06/11] ath9k: Skip malformed frames on normal FFT report Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 07/11] ath9k: No need for that extra memcpy Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 8/11] ath9k: Skip FFT reports if we are out of output buffers Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 9/11] ath9k: No need for that extra memset Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 10/11] ath9k: Mix the received FFT bins to the random pool Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-04-29 23:51 ` [ath9k-devel] [PATCH 11/11] ath9k: Enable short repeat by default on ath9k_htc Nick Kossifidis
2015-04-29 23:51   ` Nick Kossifidis
2015-05-01 12:46 ` Bob Copeland [this message]
2015-05-01 12:46   ` [PATCH 00/11] ath9k: Spectral scan updates Bob Copeland

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=20150501124622.GD14037@localhost \
    --to=me@bobcopeland.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.