linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008
Date: Wed, 9 Jul 2008 15:09:15 -0400	[thread overview]
Message-ID: <20080709190915.GA8238@tuxdriver.com> (raw)

The third Linux Wireless mini-summit will occur on Tuesday July 22,
2008 in Ottawa, just before the Ottawa Linux Symposium.  OLS is
generously supporting Linux mini-summits by providing the room and
projector (http://www.linuxsymposium.org/2008/minisummits.php).
Several vendors are supporting the event by sponsoring their own
employees to attend, and Canonical and Intel have both helped with
travel funds for key community participants as well.

Although it is already a bit late, I would like to re-open discussions
on our agenda for the meeting.  Based on current upstream topics and
those persons whom I expect to be attending, I have cobbled together
an agenda proposal below.  Please review it and feel free to suggest
amendments or alterations, or to elaborate or ask questions about my
proposed schedule of topics.

I look forward to seeing many of you in Ottawa!

John

P.S.  If you intend to attend the event in Ottawa, please send me a
private reply to this note -- even if you believe that I already know
that you are coming! :-)

---

3rd Linux Wireless Summit
Ottawa, Canada
22 July 2008

Proposed Agenda

0830	Meet & Greet

	Introductions and opening remarks

0900	Status Reports

	Overview of where things stand today

	- 802.11n

	- QoS/Multiqueue

	- Mesh mode (802.11s)

	- RF kill

1015	Break

1100	Vendor/Distro Round Table

	Representatives from hardware vendors and Linux distributions
	discuss issues around cooperation between themselves and the
	development community, what we are doing well, and what problems we
	are causing for each other.

1200	Lunch/Break (sorry, no funding)

1300	Current Work

	Short presentations/discussions about work in progress

	- encrypted management frames (802.11w)

	- regulatory enforcement (802.11d, CRDA)

	- virtual hardware (mac80211_hwsim)

1445	Break

1500	Future work

	Short presentations/discussions about work that has previously
	been suggested or requested

	- cfg80211/nl80211
		- time to push to replace WEXT?
		- tool enhancements and/or userland support?

	- power management (suspend/resume)

	- lib80211 (code sharing w/ full MAC drivers)

	- rate scaling algorithms
		- minstrel
		- others?

	- userland MLME

	- userland driver implementation

1645	Break

1700	Maintainence Issues

	Round table discussion of issues related to maintenance of
	the wireless trees

	- trivial/cleanup patches
		- testing or other requirements?
		- should they have lower priority?
		- should they require ACKs from primary author?

	- submissions to -stable
		- who should drive it?
		- what policies?

	- rate scaling algs
		- driver-specific ok?  what limitations?
		- build policies (part of mac80211.ko?)

	- questions/suggestions/complaints

1800	Dinner/Break (sorry, no funding)

2000	BoF/Break-out Sessions

	Impromptu and/or unscheduled discussions as desired by group
	participants

-- 
John W. Linville
linville@tuxdriver.com

             reply	other threads:[~2008-07-09 19:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 19:09 John W. Linville [this message]
2008-07-10  0:13 ` Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 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
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=20080709190915.GA8238@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --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).