From: matthieu castet <castet.matthieu@free.fr>
To: linux-wireless@vger.kernel.org
Subject: [Fwd: airo with WPA support merge]
Date: Sat, 05 Jul 2008 12:02:15 +0200 [thread overview]
Message-ID: <486F46A7.4020105@free.fr> (raw)
In-Reply-To: <4807C194.4040108@free.fr>
> To: prjmgr@linuxdriverproject.org
matthieu castet wrote:
> Hi,
>
> I added wpa support to airo driver some years ago, but I maintain the
> support as a OutOfTreeDrivers [1]. I use it everyday in wpa mode.
>
> It can't be merged in main because the wpa support is selected by a
> module option. I did this because supporting wpa and other mode together
> may need a large rewrite of the driver (when I did first
> experimentation, I got firmware hang if I mix wpa command that use a new
> firmware API and wep command that use old firmware API).
>
>
> But they have been some work to make it ok for main Linux tree [2], but
> it failed because of some issues [3].
>
> I don't have time nor interest to continue the work made in [2].
> May be somebody is interested.
>
> Matthieu
>
> [1]
> https://gna.org/projects/airo-wpa/ and
> http://svn.gna.org/viewcvs/airo-wpa/branches/kernel/
>
> [2]
> http://svn.gna.org/viewcvs/airo-wpa/branches/kernel-merge/
>
> [3]
> Dan Williams :
> One problem I have is that after setting the TKIP key, I always get a
> sequence of 3 bad MICs, and then the MAC sends a status of 0x8117 which
> causes the driver to send a disconnection event to userspace, which
> makes wpa_supplicant fail the connection. If I comment out the 'goto
> badrx;' in the interrupt handler where the WPA mic is checked,
> everything works great and I can complete the 4-way handshake. It needs
> more investigation, but do you have any thoughts on what might be going
> on here?
>
next parent reply other threads:[~2008-07-05 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4807C194.4040108@free.fr>
2008-07-05 10:02 ` matthieu castet [this message]
2008-07-05 17:07 ` [Fwd: airo with WPA support merge] Dave
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=486F46A7.4020105@free.fr \
--to=castet.matthieu@free.fr \
--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.