Hello, Linux wireless is, without any doubt, a very important subject. Many people show interest in it. It is good to hear that the third Linux Wireless mini-summit will occur at OLS, which will give opportunity to many people (which some of them don't know much about linux wireless) to attend it (whereas the two last wireless mini-summits were not part of OLS, as far as I know). I want to add that It would be great if part of it (or hopefully, all of it) will be videoed and put on the web. I am sure that many (including me) will be glad to watch it. I am sure that making an effort like this is important and is of interest for the linux wireless community. Regards, Mark Ryden On Wed, Jul 9, 2008 at 10:09 PM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > 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@xxxxxxxxxxxxx > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
