From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: py80211 update on github
Date: Mon, 6 Jan 2014 11:55:56 +0100 [thread overview]
Message-ID: <52CA8BBC.7070601@broadcom.com> (raw)
In-Reply-To: <1389004577.5891.6.camel@jlt4.sipsolutions.net>
On 01/06/2014 11:36 AM, Johannes Berg wrote:
> On Mon, 2014-01-06 at 10:30 +0100, Arend van Spriel wrote:
>
>> 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.
>
> This makes sense because the kernel policy only covers things that are
> sent *to* the kernel. In some very rare cases, the stuff sent *to* the
> kernel and *by* the kernel may even differ, so you may have to add some
> special cases.
Yeah, I realized that indeed the policies in the kernel only cover
validation *to* the kernel. In iw the policies are used rarely and most
type information is covered in the code. py80211 relies on policies to
obtain the type information and I was hoping to extract it from the
kernel/iw code. I may end up maintaining it in py80211.
Gr. AvS
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-01-06 10:55 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 ` py80211 update on github Arend van Spriel
2014-01-06 10:36 ` Johannes Berg
2014-01-06 10:55 ` Arend van Spriel [this message]
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=52CA8BBC.7070601@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--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).