From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <linux-wireless@vger.kernel.org>
Cc: Jouni Malinen <j@w1.fi>
Subject: Google Summer of Code 2009 -- Linux wireless roaming project
Date: Fri, 20 Mar 2009 14:57:05 -0700 [thread overview]
Message-ID: <20090320215705.GE8120@tesla> (raw)
This is what we have for roaming on our todo list:
http://wireless.kernel.org/en/developers/todo-list#Roaming
This is what we have for our GSoC roaming project:
http://wireless.kernel.org/en/developers/GSoC/2009/Improve_wireless_roaming
We need to extend this now and since things are shifting towards nl80211
(the MLME SAP stuff) I think we may need to rethink this a bit. Ideas,
wishlists for how to improve our roaming with the help of GSoC students
would be appreciated.
Luis
next reply other threads:[~2009-03-20 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 21:57 Luis R. Rodriguez [this message]
2009-03-21 11:43 ` Google Summer of Code 2009 -- Linux wireless roaming project Helmut Schaa
2009-03-24 9:06 ` Holger Schurig
2009-03-24 10:15 ` Helmut Schaa
2009-03-24 10:36 ` Holger Schurig
2009-03-24 11:05 ` Helmut Schaa
2009-03-24 12:52 ` Mats Karlsson
2009-03-24 10:37 ` Dan Williams
2009-03-24 10:46 ` Holger Schurig
2009-03-24 10:49 ` 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=20090320215705.GE8120@tesla \
--to=lrodriguez@atheros.com \
--cc=j@w1.fi \
--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).