From: "Jouni Malinen" <jkm@devicescape.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Michael Buesch <mb@bu3sch.de>,
linville@tuxdriver.com, netdev@vger.kernel.org,
bcm43xx-dev@lists.berlios.de,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] bcm43xx: Drain TX status before starting IRQs
Date: Fri, 3 Nov 2006 08:56:27 -0800 [thread overview]
Message-ID: <20061103165627.GC16894@instant802.com> (raw)
In-Reply-To: <1162457146.3241.13.camel@ux156>
On Thu, Nov 02, 2006 at 09:45:46AM +0100, Johannes Berg wrote:
> On Wed, 2006-11-01 at 23:46 -0600, Larry Finger wrote:
> > Has anyone used this patch, particularly with WPA encryption? When I try it, wpa_supplicant
> > immediately uses 90+% of the cpu and never actually authenticates with my AP. I wonder if it is
> > something with my system.
What does wpa_supplicant do here? Have you looked at the debug log? Is
it in some kind of busy loop doing something?
> Unless wpa supplicant is stupid [1] this cannot cause it any problems.
>
> johannes
>
> [1] by that, I mean sending out frames, turning off and on the
> interface, and then hoping to get a transmit status for frames sent
> before off/on cycle.
wpa_supplicant does not receive or query TX status (at least yet; in the
user space MLME case this is likely to change at some point).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-11-03 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 15:29 [PATCH] bcm43xx: Drain TX status before starting IRQs Michael Buesch
[not found] ` <200610191729.35402.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-10-20 0:25 ` Benjamin Herrenschmidt
2006-11-02 5:46 ` Larry Finger
[not found] ` <45498633.7040808-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-11-02 8:45 ` Johannes Berg
2006-11-03 16:56 ` Jouni Malinen [this message]
[not found] ` <20061103165627.GC16894-T6t7IcXamKWaos4igUoMUw@public.gmane.org>
2006-11-04 16:38 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2006-11-05 21:34 Larry Finger
2006-11-06 15:45 Larry Finger
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=20061103165627.GC16894@instant802.com \
--to=jkm@devicescape.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@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.