From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: interested in py80211?
Date: Mon, 11 Nov 2013 09:54:08 +0100 [thread overview]
Message-ID: <1384160048.14334.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <52809874.6080908@broadcom.com>
On Mon, 2013-11-11 at 09:42 +0100, Arend van Spriel wrote:
> It has been a while that I touched this topic. It is a spare-time
> project and that is somewhat limited. Since then I added genl support to
> libnl python API. I want to extract part of py80211 from nl80211.[ch]
> files. The easy part were the attribute ids and enum values from
> nl80211.h. The hurdle I want to leap know is extracting message layout
> information from nl80211.c. Do the struct nla_policy definitions hold
> all the information or would it be better to get it from the .doit
> callbacks.
Well, you probably can't get it in a scripted fashion from the doit
callbacks. The policy certainly has the first level information, but as
soon as you have nested information it will no longer work. The policy
also doesn't always cover data fram the kernel (i.e. kernel->userspace
encoding) since the kernel doesn't have to verify that.
johannes
next prev parent reply other threads:[~2013-11-11 8:54 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 [this message]
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
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=1384160048.14334.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=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).