All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Request for help: gui toolkit creation for atheros PHY/MAC statistics
Date: Fri, 23 Mar 2012 10:18:34 -0700	[thread overview]
Message-ID: <4F6CB06A.6030102@candelatech.com> (raw)
In-Reply-To: <CAJ-VmomM49oRdHKQFwbEjr7cWc8NeLFvbAgiVrg7+FsQifgpCA@mail.gmail.com>

On 03/23/2012 10:07 AM, Adrian Chadd wrote:
> Hi all,
>
> I'd like some help in writing a GUI toolkit for recording, playing
> back and visualising some of the PHY/MAC statistics the Atheros NICs
> expose.
>
> What I can do: help with the MAC/PHY side of things, identify what
> initial things would be good to support and what would actually be
> useful.
> What I can't do: dedicate time to write a GUI. :-)
> What I'd like to see: something completely free/open source written so
> we can improve the foss wireless development process.
> (Why I'm doing this: I'm fed up staring at printf() debugging in
> ath9k/FreeBSD and it's hard to have others visualise what's going on
> ..)
>
> I'd like it to be in C++/QT (before you ask - if you can make python
> or ${OTHER_LANG} handle the sheer rates of wifi traffic, MAC counters
> and PHY errors, _live_, and on tablet/atom class hardware, then please
> by all means do so..) and I'd like it to be platform portable. That
> way it can be used as a visualisation tool on other platforms, even if
> it's unable to do live capture itself (think MacOSX/Windows.)

I wouldn't ask someone to do it and then tell them what language.  Just suggest
to them what it needs to do instead.

The big question for me is:  How do you propose to get the info out
of the driver and up to user-space?

Just in case it matters...while benchmarking my Linux ethtool patch to ath9k,
I found it took around 35us to make the ethtool ioctl call to get the
stats.  This was on a dual-core Atom system.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2012-03-23 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 17:07 [ath9k-devel] Request for help: gui toolkit creation for atheros PHY/MAC statistics Adrian Chadd
2012-03-23 17:18 ` Ben Greear [this message]
2012-03-23 17:25   ` Adrian Chadd
2012-03-24  4:46     ` [ath9k-devel] [ath5k-devel] " Qasim Javed

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=4F6CB06A.6030102@candelatech.com \
    --to=greearb@candelatech.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.