linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mabbas <mabbas@linux.intel.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	Jouni Malinen <jkm@devicescape.com>,
	Simon Barber <simon@devicescape.com>
Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery and  association
Date: Wed, 11 Apr 2007 15:23:01 -0700	[thread overview]
Message-ID: <461D5FC5.5070404@linux.intel.com> (raw)
In-Reply-To: <200704111630.06160.flamingice@sourmilk.net>

Michael Wu wrote:
> On Wednesday 11 April 2007 16:04, mabbas wrote:
>   
>> I am not familiar with userspace mlme what needed to be done?
>>     
> mac80211 has a userspace mlme mode which defers all things dealing with 
> management frames to userspace (wpa_supplicant). It basically disables all 
> the code in ieee80211_sta.c and routes management frames to a special 
> interface where wpa_supplicant (or hostap) handles things. This is preferred 
> and the ieee80211_sta.c code is there for backwards compatibility.
>
> No major features should be added to the in-kernel MLME (ieee80211_sta.c) but 
> even more importantly, your patch series does not provide the appropriate 
> hooks for a userspace MLME to support a driver using this 802.11n API.
>
> -Michael Wu
>   
where i can get mac80211 userspace mlme?
Mohamed

  parent reply	other threads:[~2007-04-11 22:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 11:38 [patch 2/5] Add basic support for IEEE 802.11n discovery and association mohamed
2007-03-26 23:52 ` Randy Dunlap
2007-04-04 10:37   ` mabbas
2007-03-27 17:05 ` Luis R. Rodriguez
2007-03-27 17:11   ` Luis R. Rodriguez
2007-03-27 17:29     ` Luis R. Rodriguez
2007-03-29  6:04       ` mohamed
2007-03-28 19:11         ` Luis R. Rodriguez
2007-03-29  7:21           ` mohamed
2007-03-28  9:14 ` Johannes Berg
2007-03-29  5:56   ` mohamed
2007-03-28 20:03 ` Johannes Berg
2007-03-29 19:46   ` Luis R. Rodriguez
     [not found]     ` <1ba2fa240703291648h6b0d10bdje2ea54f3c1754f5b@mail.gmail.com>
2007-03-30 10:38       ` Johannes Berg
     [not found]         ` <1ba2fa240703300418r781931cdp50430dcb02259f1@mail.gmail.com>
2007-03-30 12:11           ` Johannes Berg
2007-03-31 15:37 ` Michael Wu
2007-04-11 19:40   ` John W. Linville
2007-04-11 20:04     ` mabbas
2007-04-11 20:29       ` Michael Wu
2007-04-11 22:03         ` Tomas Winkler
2007-04-11 22:50           ` Simon Barber
2007-04-11 23:05             ` Tomas Winkler
2007-04-11 23:25               ` Andy Green
2007-04-12  8:56                 ` Johannes Berg
2007-04-12  9:01                   ` Andy Green
2007-04-12  9:06                     ` Johannes Berg
2007-04-12  0:20               ` Simon Barber
2007-04-12  1:13                 ` Tomas Winkler
2007-04-11 22:23         ` mabbas [this message]
2007-04-11 22:56           ` Michael Wu
2007-04-12 18:11             ` mabbas

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=461D5FC5.5070404@linux.intel.com \
    --to=mabbas@linux.intel.com \
    --cc=flamingice@sourmilk.net \
    --cc=jkm@devicescape.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=simon@devicescape.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 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).