All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless mini-summit agenda proposals?
Date: Thu, 31 Jan 2008 12:52:03 -0500	[thread overview]
Message-ID: <1201801923.3000.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20080131162514.GC6413@tuxdriver.com>

On Thu, 2008-01-31 at 11:25 -0500, John W. Linville wrote:
> Greetings,
> 
> It looks as if we have a few venue options for a third wireless summit.
> While this may seem like a luxury, none of the options are perfect
> for everyone and each has it's own potential drawbacks.  So rather
> than move blindly forward with any given venue, I think it would be
> good to discuss some potential agenda points.
> 
> This will serve both to determine who is most interested in attending
> a summit and who might most need to be there.  This will also serve
> to justify the trouble of having a summit at all.  So, I'd like to
> open the 'floor' to discussion proposals.
> 
> What discussions pertinent to Linux wireless development do
> you want to see?  What can you contribute to those discussions?
> How would a face-to-face discussion of that issue be better than an
> online discussion?

cfg80211/nl80211 - overview, get Johannes to disseminate knowledge
because email isn't optimal for this.  I haven't had enough time to jump
into it yet, but the fact that Johannes is the vast majority of the
effort here is worrisome.  Having a reference implementation (airo,
atmel, maybe libertas) of a fullmac driver ported to cfg80211 would
probably be very useful, even just to get a sense of how the API works.

rfkill - how to clean up the mess, including how it's all supposed to
work from userspace with kernel bits, ACPI bits, vendor modules like
asus_acpi and dellWirelessCtl, input-only buttons, etc

WiMAX - what hardware is coming, what the APIs should look like (OMA-DM
is likely to be part of Sprint's stack for XOHM), what the driver
situation is, and how to fend off a repeat of the 802.11 regulatory
situation for WiMAX (most parts are apparently fullmac right now, but
softmac will surely come).

802.11s - nail down issues that Javier/Luis/others might have and try to
push the 802.11s mesh stack forward (driver issues, API issues, etc)

802.11n - do we need any discussion here or is it just a question of
executing on the current plan?

Userspace MLME - what's going on here?  Noise around this seems to be
quieter these days.  Is stuff going according to plan/schedule or are
there roadblocks?

lib80211/fullmac - maybe this just needs to be picked up and done by
somebody and doesn't need any discussion or whatever

Dan



  reply	other threads:[~2008-01-31 17:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 16:25 wireless mini-summit agenda proposals? John W. Linville
2008-01-31 17:52 ` Dan Williams [this message]
2008-01-31 19:42   ` Inaky Perez-Gonzalez
2008-02-01 12:42   ` Johannes Berg
2008-02-01 18:29     ` Tomas Winkler
2008-02-01 19:15       ` Dan Williams
2008-02-01 19:47         ` Tomas Winkler
2008-02-01 20:11           ` Dan Williams
2008-02-01 21:21             ` Tomas Winkler
2008-02-01 21:31               ` Dan Williams
2008-03-28 20:32   ` John W. Linville
2008-03-31 20:12     ` John W. Linville
2008-04-01 12:23       ` Johannes Berg
2008-04-01 14:12         ` Johannes Berg
2008-04-01 23:00           ` Nick Kossifidis
2008-04-02  0:18             ` John W. Linville
2008-02-01 16:16 ` Johannes Berg
2008-02-01 19:07   ` Nick Kossifidis
2008-02-01 20:11     ` Johannes Berg
2008-02-01 20:29       ` Luis Carlos Cobo
2008-02-02  3:32         ` Luis Carlos Cobo
2008-02-01 21:28       ` Tomas Winkler

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=1201801923.3000.13.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.