linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: 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, 31 Jul 2013 11:35:49 +0200	[thread overview]
Message-ID: <51F8DA75.8040903@broadcom.com> (raw)
In-Reply-To: <CAB=NE6Vm18RcDYQn+QoEzSG202HezT0rqV_hwb_UOzyecstu5w@mail.gmail.com>

On 07/31/2013 02:53 AM, Luis R. Rodriguez wrote:
> Folks,
>
> Back in 2009 Intel had put out a wifi-test tree [0] but that seems
> deprecated now. The git tree at least is gone. Can someone confirm if
> that's dead? We later had Google present at the 2010 San Francisco
> wireless summit [1] their test infrastructure using autotest. Last I
> checked that stuff was not merged back upstream to autotest. Can
> someone confirm ? Lastly we have mac80211_hwsim [2] and also a slew of
> internal testing infrastructures that obviously are not open.
>
> If we are to embark on a new journey towards an open testing
> infrastructure what should be used? Ben, you have some stuff, and I
> know you also report some interesting bugs with insane amount of
> stations. Is any of it open?
>
> AFAICT mac80211_hwism should and likely already is used for a slew of
> core API changes / tests. Addressing testing using that shoud
> hopefully address tons of testings and find a lot of issues. We'd then
> just need vendors to replicate behaviour on top of their drivers. The
> core test stuff though still needs to be available.
>
> What do we have, anyone have any lofty plans?

We have a large testing infrastructure consisting of shielded boxes, 
attenuators, etc. It is all exercised using tcl scripts and none of it 
is open today. Who knows what tomorrow will bring. The brcm80211 
open-source drivers are tested limited but nightly using it.

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.

Regards,
Arend

> [0] http://wireless.kernel.org/en/developers/Testing/wifi-test
> [1] http://wireless.kernel.org/en/developers/Summits/SanFranciscoBayArea-2010
> [2] http://wireless.kernel.org/en/users/Drivers/mac80211_hwsim
>
>    Luis
> --
> 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
>



  parent reply	other threads:[~2013-07-31  9:36 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 [this message]
2013-08-05  7:59   ` Kalle Valo
2013-08-07 10:39     ` Arend van Spriel
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=51F8DA75.8040903@broadcom.com \
    --to=arend@broadcom.com \
    --cc=greearb@candelatech.com \
    --cc=j@w1.fi \
    --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).