Netdev List
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Udayan Singh <udayan.singh@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Setup of testing lab and work on development
Date: Wed, 15 Nov 2006 22:15:09 +0100	[thread overview]
Message-ID: <1163625309.5399.121.camel@johannes.berg> (raw)
In-Reply-To: <d9a09df00611151304l11d089b5w958788ec24fc6af0@mail.gmail.com>

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

On Thu, 2006-11-16 at 02:34 +0530, Udayan Singh wrote:

> ok. you are referring to bcm43xx , etc

right, all of those drivers use d80211.

> lets say we have development happening in d80211 driver. now if i want
> to participate in the development of the (d80211), i can do it in a
> much better manner if i am trying out modificaitons on my own on the
> drivers that are using d80211 (my feeling) 

I doubt you'll get far without ever testing your code changes. :)

> e.g. bcm43xx, etc. Hence i
> would like to setup a test environment where i can make modifications
> in code (of d80211 or related driver) and test it....

You'll need one of the cards that is supported by a d80211 driver. I've
used bcm43xx and rt2500usb so far.

> same - "participate in development on d80211"

Well, check http://wireless.sipsolutions.net for things we still have to
do... and then send patches :)

Or do something else you're interested in and send patches.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2006-11-15 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 16:57 Setup of testing lab and work on development Udayan Singh
2006-11-15 18:15 ` Johannes Berg
2006-11-15 21:04   ` Udayan Singh
2006-11-15 21:15     ` Johannes Berg [this message]
2006-11-18 18:02       ` Udayan Singh
2006-11-20  3:22         ` Udayan Singh

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=1163625309.5399.121.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    --cc=udayan.singh@gmail.com \
    /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