linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "ivan.muccini@witech.it" <ivan.muccini@witech.it>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 802.11s is possible
Date: Thu, 22 Feb 2007 13:11:11 -0500	[thread overview]
Message-ID: <20070222181111.GE5631@tuxdriver.com> (raw)
In-Reply-To: <45ddd0c2.b2.681a.1375331394@webmailh5.aruba.it>

On Thu, Feb 22, 2007 at 06:20:02PM +0100, ivan.muccini@witech.it wrote:
> Hi, i'm italian student. I want experiment a channel
> assignment algorithm in 802.11s mesh network. I think to use
> madwifi driver for develop 802.11 feature, like new mesh
> header in MAC header of Data frame, beacon, probe message
> and association. Moreover I need to create new information
> elemnt for HWMP routing protcol.
> Becouse i am new in madwifi, i'm asking you if is possible
> do this whit madwifi.

You'll have to look elsewhere for madwifi.  This list is for work
destined for inclusion in the Linux kernel itself.  If you must use
Atheros hardware, then please consider working in the ar5k-based
dadwifi branch of the madwifi project.  That may have a future in
the upstream kernel.

However, please consider using the Devicescape-originated stack which
we here are working to have included in the upstream kernel "soon".  If you
are familiar with git, you can get the sources from the tree here:

	git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git

If you would prefer a stack of patches (over 700!) to apply on top
of a current tree from Linus, you may want to look here:

	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-dev/mm-master

If that is unappealing but you are a Fedora user, you may want to
look at my test kernels here:

	http://people.redhat.com/linville/kernels/fc6/

Or my Fedora-netdev kernels available through yum by following the
instructions here:

	http://people.redhat.com/linville/kernels/fedora-netdev/

And if none of those apply, you may wish to stick to Ralink rt2x00 or
Intel ipw3945 hardware.  Each of those projects maintains a snapshot
of the Devicescape-originated stack for use with their own drivers.

As for help with understanding the stack code, Devicescape has some
documentation available at their site.	And, of course, the code
itself is the best reference.  :-)

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2007-02-22 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 17:20 802.11s is possible ivan.muccini
2007-02-22 18:11 ` John W. Linville [this message]

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=20070222181111.GE5631@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ivan.muccini@witech.it \
    --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).