From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>, "Jouni Malinen" <j@w1.fi>
Cc: 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: Wed, 28 May 2008 09:17:10 +0300 [thread overview]
Message-ID: <1ba2fa240805272317t359e79d2xb1913779939ac7c9@mail.gmail.com> (raw)
In-Reply-To: <1211909055.3930.23.camel@johannes.berg>
On Tue, May 27, 2008 at 8:24 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> 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).
>
> Good point. That should actually be doable quite easily.
>
>> This would avoid need to add new IEs one by one in the future (e.g., for
>> IEEE 802.11r).
>
> Yeah, precisely.
>
>> 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).
>
> Actually, we do store them in one blob and then hand out pointers to the
> various parts.
>
> johannes
>
Would this work with current and older version of wpa_supplicant?.
I'm concern with backward compatibility,
Thanks
Tomas
next prev parent reply other threads:[~2008-05-28 6:17 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
2008-05-27 17:24 ` Johannes Berg
2008-05-28 6:17 ` Tomas Winkler [this message]
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=1ba2fa240805272317t359e79d2xb1913779939ac7c9@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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