All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Powell <Mark.Powell@csr.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, Jouni Malinen <j@w1.fi>
Subject: Re: WPA/RSN information in cfg80211?
Date: Wed, 28 Mar 2007 11:04:54 +0100	[thread overview]
Message-ID: <460A3DC6.8030604@csr.com> (raw)
In-Reply-To: <1175075263.5151.31.camel@johannes.berg>

Johannes Berg wrote:
> On Wed, 2007-03-28 at 10:33 +0100, Mark Powell wrote:
>   
>> We certainly need the individual settings. It is nice that
>> wpa_supplicant generates the IE - it saved me writing the code - but
>> that's just being lazy. We still have to modify the IE anyway to add WMM
>> stuff.
>>     
> Do I read that as "I don't care if we get the IE"?
>   
We can build it into the driver if we have to :)
> Putting the IE there has the advantage that you can easily play with new
> things for cards that use the IE by sticking a few more IEs into the
> attribute. 
I agree. Forming the MLME requests, including the IE, is really the role
of the userland app (the SME in IEEE802.11 speak).
> But it has the disadvantage that cards behave differently if
> you give them contradictory settings. Maybe we need a way to ask a card
> which one it wants.
>   
Is that just a case of garbage-in-garbage-out?

Mark



To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview

  reply	other threads:[~2007-03-28 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 22:34 WPA/RSN information in cfg80211? Johannes Berg
2007-03-28  9:33 ` Mark Powell
2007-03-28  9:47   ` Johannes Berg
2007-03-28 10:04     ` Mark Powell [this message]
2007-03-28 10:24       ` Johannes Berg
2007-03-28 14:47 ` Dan Williams
2007-03-28 19:00 ` Jouni Malinen
2007-03-29 11:12   ` Johannes Berg
2007-03-29 15:44     ` Jouni Malinen

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=460A3DC6.8030604@csr.com \
    --to=mark.powell@csr.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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.