From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH v2] p54: connect to 11w protected networks
Date: Fri, 07 Sep 2012 14:17:14 +0200 [thread overview]
Message-ID: <1347020234.4256.22.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1346770467.3737.32.camel@jlt4.sipsolutions.net> (sfid-20120904_165356_208297_322195F0)
On Tue, 2012-09-04 at 16:54 +0200, Johannes Berg wrote:
> > > We can't get this to happen without a module option? Is there a way to
> > > turn the crypto offloading off when we know we're connecting to a W
> > > protected AP?
> >
> > Yeah that's what I was thinking. I suppose we *could* somehow do this by
> > setting some key flag in mac80211 that the driver can check.
>
> Something like this perhaps:
>
> http://p.sipsolutions.net/76d17d49f4685cda.txt
If you want this for your driver, I'll commit this:
http://p.sipsolutions.net/ea2e3dbe980f5db8.txt
johannes
next prev parent reply other threads:[~2012-09-07 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 13:22 [PATCH] p54: connect to 11w protected networks Christian Lamparter
2012-09-02 21:48 ` Johannes Berg
2012-09-04 13:19 ` [PATCH v2] " Christian Lamparter
2012-09-04 14:15 ` Johannes Berg
2012-09-04 14:33 ` Dan Williams
2012-09-04 14:37 ` Johannes Berg
2012-09-04 14:54 ` Johannes Berg
2012-09-07 12:17 ` Johannes Berg [this message]
2012-09-07 15:47 ` Christian Lamparter
2012-09-07 15:55 ` Johannes Berg
2012-09-07 16:10 ` Christian Lamparter
2012-09-07 16:15 ` Johannes Berg
2012-09-07 16:26 ` Christian Lamparter
[not found] ` <201209071825.13588.chunkeey@googlemail.com>
[not found] ` <1347035277.4256.33.camel@jlt4.sipsolutions.net>
2012-09-07 17:01 ` Christian Lamparter
2012-09-07 17:09 ` Johannes Berg
2012-09-07 17:28 ` 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=1347020234.4256.22.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.