Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Jouni Malinen" <j@w1.fi>,
	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 17:18:30 +0300	[thread overview]
Message-ID: <1ba2fa240805280718u2ee9232ao487575afeb5938f3@mail.gmail.com> (raw)
In-Reply-To: <1211980492.21624.11.camel@johannes.berg>

On Wed, May 28, 2008 at 4:14 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).
>
>> Would this work with current and older version of  wpa_supplicant?.
>> I'm concern with backward compatibility,
>
> Yes, even iwlist handles that fine. In fact, wpa_supplicant simply
> concatenates all of them internally, and iwlist just prints each IE it
> finds in each GENIE item.

One more obstacle

> Actually, we do store them in one blob and then hand out pointers to the
> various parts.

we don't store them as one block we allocate each one separately
(ieee80211_sta_bss) so there will be some bigger rewrite of the code
than this patch, which I'm a bit reluctant to do...time...bugs etc
so what more arguments we have to convince me :)

Thanks
Tomas


>
> johannes
>

  reply	other threads:[~2008-05-28 14:18 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
2008-05-28 13:14         ` Johannes Berg
2008-05-28 14:18           ` Tomas Winkler [this message]
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=1ba2fa240805280718u2ee9232ao487575afeb5938f3@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