From: "John W. Linville" <linville@tuxdriver.com>
To: Guy Cohen <guy@cguy.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008
Date: Tue, 15 Jul 2008 13:42:46 -0400 [thread overview]
Message-ID: <20080715174246.GA3117@tuxdriver.com> (raw)
In-Reply-To: <247d6d340807140805gfb6523en74384f6f47469d79@mail.gmail.com>
On Mon, Jul 14, 2008 at 06:05:13PM +0300, Guy Cohen wrote:
> I think that probably the most burning topics were a little diminished
> in our agenda, and should be put higher:
> - cfg80211/nl80211 - much of the current wext begins to fall behind
> the emerging capabilities of the mac80211 and moreover - from future
> abilities and needs of future fullmac devices. The functionality and
> ABI to userspace must be finalized as soon as possible. The status of
> this is very unclear and should be treated more thoroughly, and it
> seems it can't be shared with 5 other topics in less than 2 hours.
FWIW, I listed this one first under Future Work.
> - fullmac support - seems to be very relevant in the next couple of
> years with the integration of wifi into low power devices running
> linux.
Not sure exactly what you mean with this one. Are you talking about
the lib80211 line item? Or enhancements to the mac80211 component
to support full(er) MAC designs?
> I think that these two topics should take precedence over other topics
> that although important consume more time in the agenda, and are
> currently less likely to have impact on the average users such as 11s
> and 11w.
>
> it would be good if these topics will get substantial time slot in the agenda.
There are lots of items listed, and I'm not sure we will cover all
of them. If there are any that you would like to suggest be dropped
completely then please do so.
That said, I don't think we have enough time for real working sessions
on Tuesday. I think it would be better just to touch on a variety
of topics that can benefit from some face-to-face discussions.
>From that perspective, I think some status reports and some brief
proposals are most appropriate.
I'll post a revised (mostly just augmented) agenda proposal today.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-07-15 18:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 19:09 Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 John W. Linville
2008-07-10 0:13 ` Tomas Winkler
2008-07-10 6:52 ` Ron Rindjunsky
2008-07-10 14:30 ` Kalle Valo
2008-07-11 1:41 ` Jouni Malinen
2008-07-11 4:46 ` Kalle Valo
2008-07-10 6:41 ` Mark Ryden
2008-07-10 7:21 ` Holger Schurig
2008-07-10 7:23 ` Johannes Berg
2008-07-10 10:22 ` Johannes Berg
2008-07-10 10:50 ` Tomas Winkler
2008-07-10 14:31 ` Johannes Berg
2008-07-10 15:15 ` Tomas Winkler
2008-07-10 15:52 ` Inaky Perez-Gonzalez
2008-07-10 16:12 ` Stefanik Gábor
2008-07-10 16:15 ` Michael Buesch
2008-07-15 17:16 ` Dan Williams
2008-07-15 17:31 ` Nicolas Pitre
2008-07-15 17:58 ` Dan Williams
2008-07-15 18:02 ` Dan Williams
2008-07-15 18:14 ` Nicolas Pitre
2008-07-15 18:38 ` Dan Williams
2008-07-21 14:23 ` Dan Williams
2008-07-21 16:46 ` Nicolas Pitre
2008-07-15 18:20 ` Kalle Valo
2008-07-14 15:05 ` Guy Cohen
2008-07-15 17:42 ` John W. Linville [this message]
2008-07-15 18:15 ` Dan Williams
2008-07-16 8:24 ` Johannes Berg
2008-07-16 16:27 ` Dan Williams
2008-07-14 15:43 ` Guy Cohen
2008-07-15 18:26 ` REVISED AGENDA -- " John W. Linville
2008-07-16 8:40 ` Johannes Berg
2008-07-16 11:29 ` Tomas Winkler
2008-07-16 18:48 ` 2nd " John W. Linville
2008-07-16 19:58 ` John W. Linville
2008-07-17 10:05 ` Luis R. Rodriguez
2008-07-17 10:16 ` Luis R. Rodriguez
2008-07-18 23:23 ` 3rd " John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2008-07-10 7:41 Joerg Pommnitz
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=20080715174246.GA3117@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=guy@cguy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).