From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Javier Cardona <javier@cozybit.com>,
linux-wireless@vger.kernel.org, marcelo@kvack.org
Subject: Re: libertas (private) ioctls vs. nl80211
Date: Tue, 10 Jul 2007 10:56:15 -0400 [thread overview]
Message-ID: <20070710145615.GB7927@tuxdriver.com> (raw)
In-Reply-To: <1183738085.23402.2.camel@xo-13-A4-25.localdomain>
On Fri, Jul 06, 2007 at 12:08:05PM -0400, Dan Williams wrote:
> On Fri, 2007-07-06 at 08:40 -0700, Javier Cardona wrote:
> > John,
> >
> > On 6/14/07, John W. Linville <linville@tuxdriver.com> wrote:
> > > I'm not aware of any project working on wireless mesh in mac80211 at
> > > the moment, serious or otherwise. I think one would be worthwhile,
> > > but I don't know of anyone working on it.
> >
> > We (cozybit Inc.) are working on an open implementation of 802.11s for
> > Linux, based on mac80211. We implemented an early draft
> > implementation of 802.11s for the Marvell wireless interface used on
> > the One Laptop Per Child. That implementation was done entirely in
> > firmware to take advantage of the unique capabilities of Marvell's
> > wireless device: the system-on-chip wireless module enables the
> > laptop to act as a low-power, fully functional mesh point even when
> > the main CPU is off.
> >
> > Our next goal is to do a reference implementation of the latest
> > 802.11s draft on Linux. The hope is that it will help to achieve
> > early interoperability and convergence of the standard. We are
> > seeking sponsors for the project. So far Nortel has expressed strong
> > interest.
>
> Rock on. If we can achieve convergence between the API that libertas
> +mesh and the mac80211+mesh use, then we should both use the same
> cfg80211/nl80211 interface for both.
ACK. This is definitely good news. I am eager to see your patches.
Let me know if I can somehow be helpful in your help for project
sponsorship.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-10 15:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 17:58 libertas (private) ioctls vs. nl80211 Johannes Berg
2007-06-14 17:09 ` Christoph Hellwig
2007-06-14 17:38 ` Andrew Morton
2007-06-14 18:13 ` Christoph Hellwig
2007-06-14 18:23 ` Linus Torvalds
2007-06-14 18:48 ` Jeff Garzik
2007-06-14 22:22 ` Dan Williams
2007-06-14 22:31 ` Christoph Hellwig
2007-06-14 22:55 ` Dan Williams
2007-06-14 19:09 ` John W. Linville
2007-06-14 19:56 ` Andrew Morton
2007-06-14 20:08 ` John W. Linville
2007-06-17 4:46 ` Matt Mackall
2007-07-06 15:40 ` Javier Cardona
2007-07-06 16:08 ` Dan Williams
2007-07-10 14:56 ` John W. Linville [this message]
2007-07-10 15:18 ` John W. Linville
2007-06-18 17:38 ` Dan Williams
2007-06-18 18:44 ` Christoph Hellwig
2007-06-18 18:57 ` Sam Ravnborg
2007-06-14 20:03 ` Holger Schurig
2007-06-14 22:48 ` Dan Williams
2007-06-15 18:42 ` Dan Williams
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=20070710145615.GB7927@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcelo@kvack.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).