From: Christian Lamparter <chunkeey@googlemail.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH v3] p54: connect to 11w protected networks
Date: Mon, 10 Sep 2012 17:59:17 +0200 [thread overview]
Message-ID: <201209101759.17751.chunkeey@googlemail.com> (raw)
In-Reply-To: <87ehma5agf.fsf@purkki.adurom.net>
On Monday 10 September 2012 14:28:00 Kalle Valo wrote:
> Dan Williams <dcbw@redhat.com> writes:
>
> > On Tue, 2012-09-04 at 15:19 +0200, Christian Lamparter wrote:
> >> Previously, it was not possible to connect
> >> to networks which requires 11w to be supported
> >> by the stations.
> >
> > If at all possible if we can do this without module parameters, that
> > would be great. Otherwise how is userspace supposed to connect to a
> > W-capable network without twiddling driver-specific module options,
> > something we've tried really hard to not do? Module options really
> > aren't any different than private ioctls or IWPRIV commands...
>
> Sure, and that's how it works with properly supported hardware. But p54
> is so old that the user will need to buy newer hardware if he really
> needs 11w support out-of-box. IMHO there's no point of making a huge
> effort to add 11w support to older hardware, there are more important
> things to fix in Linux wireless stack than that.
Dan's concern has been addressed by v4 of this patch
(which depends on johannes' "add mgmt key flags" patch).
p54 should now provide basic support for 11w protected
networks w/o messing with any module parameters.
Regards,
Chr
next prev parent reply other threads:[~2012-09-10 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 13:19 [PATCH v3] p54: connect to 11w protected networks Christian Lamparter
2012-09-07 16:51 ` Dan Williams
2012-09-07 17:05 ` Christian Lamparter
2012-09-10 12:28 ` Kalle Valo
2012-09-10 15:59 ` Christian Lamparter [this message]
2012-09-10 16:49 ` Dan Williams
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=201209101759.17751.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=dcbw@redhat.com \
--cc=kvalo@adurom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).