From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
linville@tuxdriver.com, yi.zhu@intel.com,
linux-wireless@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH 1/1] mac80211: sends HT IE to user level through wext
Date: Tue, 27 May 2008 20:20:33 +0300 [thread overview]
Message-ID: <20080527172032.GN4932@jm.kir.nu> (raw)
In-Reply-To: <1211907892.3930.19.camel@johannes.berg>
On Tue, May 27, 2008 at 07:04:52PM +0200, Johannes Berg wrote:
> I'm fine with this, but I'm wondering if maybe we should just pass out
> the whole IE area of the beacon/probe response?
I would prefer to get all IEs in one blob (assuming WEXT does not have
length limits on this data that could be up to about 2250 bytes long).
This would avoid need to add new IEs one by one in the future (e.g., for
IEEE 802.11r).
wpa_supplicant should be able to combine multiple IEs (or even multiple
IE groups) together, so I'm not too concerned of this being done
separately, but in general, it would be simpler to just pass all IEs as
a single blob. It might even be worthwhile to start storing the IEs as a
single buffer and have helper functions to fetch pointer to the
beginning of whatever IE is needed in the MLME code (this is how the
current wpa_supplicant processes IEs from scan results).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-05-27 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 17:00 [PATCH 1/1] mac80211: sends HT IE to user level through wext Tomas Winkler
2008-05-27 17:04 ` Johannes Berg
2008-05-27 17:20 ` Jouni Malinen [this message]
2008-05-27 17:24 ` Johannes Berg
2008-05-28 6:17 ` Tomas Winkler
2008-05-28 13:14 ` Johannes Berg
2008-05-28 14:18 ` Tomas Winkler
2008-05-28 14:24 ` Johannes Berg
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=20080527172032.GN4932@jm.kir.nu \
--to=j@w1.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@intel.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