netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: netdev@vger.kernel.org, zd1211-devs@lists.sourceforge.net,
	"Ivan Seskar" <Seskar@winlab.rutgers.edu>,
	"Kishore Ramachandran" <kishore@winlab.rutgers.edu>
Subject: Re: Streamline testing of 802.11 drivers
Date: Fri, 23 Jun 2006 23:38:26 +0200	[thread overview]
Message-ID: <200606232338.26801.IvDoorn@gmail.com> (raw)
In-Reply-To: <43e72e890606231333kd0fc534x5d08dad955d13bf5@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]

Hi,

> I've mentioned this to a few but here it is out to everyone. So as you
> know we have a lot of work ahead of us for linux wireless development.
> To help speed this up, we at Winlab, would like to start hosting a
> testbed for linux wireless development, open to the public. Short term
> goals would be to start off a couple of nodes for each driver
> currently under development like bcm43xx, zd1211, rt2x00, ipw3945,
> ipw2200 and the like, and a provide a set streamlined tests we can use
> to really put to test the drivers and stacks.

This would be really interesting. :)

> This wouldn't be easy if we didn't have infrastructure but we already
> do. Our grid consists of 400 nodes with 2 wireless cards each and 3
> ethernet ports (one for control) --
> http://orbit-lab.org/wiki/Tutorial/Testbed. 90% of our nodes use the
> atheros 5213 chipset and the rest ipw2200s. We'd like to expand this
> with the more wireless cards currently being worked on for linux.
> 
> Right now we have zome zd1211s so we'll start with that (I'll start
> working on a port to d80211) but will try to accomodate other nodes as
> we get more wireless cards. We will need some help too though, to
> streamline the testing. If you have ideas or would like to contribute
> please let me know. We can purchase wireless cards but if you already
> have reliable confirmed wireless cards which can be used for putting
> into the testbed let me know.

I'll discuss this in the rt2x00 team, and see if we can donate some
hardware.

Ivo

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-06-23 21:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 20:33 Streamline testing of 802.11 drivers Luis R. Rodriguez
2006-06-23 20:56 ` Luis R. Rodriguez
2006-06-23 21:38 ` Ivo van Doorn [this message]
2006-06-23 22:07   ` Luis R. Rodriguez
2006-06-23 22:48 ` Larry Finger
2006-06-23 22:56   ` Luis R. Rodriguez
2006-06-25 12:42     ` Johannes Berg
2006-06-25 15:22       ` Luis R. Rodriguez

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=200606232338.26801.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=Seskar@winlab.rutgers.edu \
    --cc=kishore@winlab.rutgers.edu \
    --cc=mcgrof@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=zd1211-devs@lists.sourceforge.net \
    /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).