From: Arend van Spriel <arend@broadcom.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: py80211 update on github
Date: Mon, 6 Jan 2014 10:30:29 +0100 [thread overview]
Message-ID: <52CA77B5.5060100@broadcom.com> (raw)
In-Reply-To: <51D49027.9010803@broadcom.com>
On 07/03/2013 10:57 PM, Arend van Spriel wrote:
> A common say in Linux arena is "when you have an itch, just scratch it".
> My itch is that tools like ifconfig and iw are great, but in an
> automated test environment it kind of sucks to parse output, which is
> confirmed by blurb from iw: "Do NOT screenscrape this tool, we don't
> consider its output stable.".
In the christmas holiday I tinkered a bit more on py80211. It comes with
a utility to extract definitions and netlink policies from the nl80211
source files. What is currently on github is in prototype state. It can
retrieve all wiphy information including band, frequency and rate
information. It relies on policy information and it turned out that not
all attributes are properly initialized in nl80211_policy. One that I
added manually is NL80211_ATTR_SUPPORTED_IFTYPES, which should actually
be typed as NLA_NESTED. There are other attributes that are not covered yet.
>
> https://github.com/arend/py80211
>
The source files are found in the github repository. It has two
branches. The master branch is based on 3.12.6 and I intend to follow
the kernel releases on that. The wl-next branch is based on the
wireless-next repository.
Regards,
Arend
next prev parent reply other threads:[~2014-01-06 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 20:57 interested in py80211? Arend van Spriel
2013-07-12 8:02 ` Johannes Berg
2013-07-12 13:32 ` Arend van Spriel
2013-07-24 15:55 ` Will Hawkins
2013-07-24 21:06 ` Arend van Spriel
2013-11-11 8:42 ` Arend van Spriel
2013-11-11 8:54 ` Johannes Berg
2014-01-06 9:30 ` Arend van Spriel [this message]
2014-01-06 10:36 ` py80211 update on github Johannes Berg
2014-01-06 10:55 ` Arend van Spriel
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=52CA77B5.5060100@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.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 NNTP newsgroup(s).