linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Kalle Valo" <kvalo@adurom.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Ben Greear" <greearb@candelatech.com>,
	"Paul Stewart" <pstew@chromium.org>,
	"Felix Fietkau" <nbd@openwrt.org>, "Jouni Malinen" <j@w1.fi>
Subject: Re: 802.11 infrastructure for regression testing - upstream / mac80211 / cfg80211
Date: Wed, 7 Aug 2013 12:39:23 +0200	[thread overview]
Message-ID: <520223DB.5050701@broadcom.com> (raw)
In-Reply-To: <87li4gwosw.fsf@purkki.adurom.net>

On 08/05/2013 09:59 AM, Kalle Valo wrote:
> "Arend van Spriel" <arend@broadcom.com> writes:
>
>> I am considering coming up with a new test framework for the brcm80211
>> drivers using python scripting, which is why I started py80211
>> experiment (available on github), but your mentioning of autotest
>> makes me want to revisit that.
>
> No no, please forget anything your heard about autotest and just focus
> on py80211 ;)
>
> More seriously, my experience with the autotest and any other test
> frameworks are that they are so freaking huge and difficult to maintain
> that eventually they just die. Small is beautiful and I have been
> dreaming about a lean and mean python based nl80211 test harness for
> drivers, but never found the time to do anything (my usual story). So
> I'm eagerly waiting how your py80211 will workout.

I am on vacation now so I may end up working on it. Although, I do have 
an almost 5yr old son claiming most of my time :-)

Anyway, there have been a few patches applied to libnl itself to support 
genl in python. So I can send and receive netlink messages and 
notifications as a python dictionary of netlink attributes. Now need to 
determine the level of abstraction I want to provide to users of 
py80211. Suggestions are more than welcome.

Regards,
Arend



  reply	other threads:[~2013-08-07 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  0:53 802.11 infrastructure for regression testing - upstream / mac80211 / cfg80211 Luis R. Rodriguez
2013-07-31  6:44 ` Johannes Berg
2013-07-31  7:25 ` Jouni Malinen
2013-07-31  9:35 ` Arend van Spriel
2013-08-05  7:59   ` Kalle Valo
2013-08-07 10:39     ` Arend van Spriel [this message]
2013-07-31 18:13 ` Ben Greear

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=520223DB.5050701@broadcom.com \
    --to=arend@broadcom.com \
    --cc=greearb@candelatech.com \
    --cc=j@w1.fi \
    --cc=kvalo@adurom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=nbd@openwrt.org \
    --cc=pstew@chromium.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).