All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: nl80211 and wext interoperability
Date: Mon, 13 Jul 2009 15:10:06 -0400	[thread overview]
Message-ID: <1247512206.4369.67.camel@localhost.localdomain> (raw)
In-Reply-To: <1247507677.4166.27.camel@johannes.local>

On Mon, 2009-07-13 at 19:54 +0200, Johannes Berg wrote:
> On Mon, 2009-07-13 at 13:53 -0400, Dan Williams wrote:
> 
> > Mainly because there's no way to tell WEXT drivers to "stop whatever
> > you're doing and just be idle"...
> > 
> > The supplicant clears out the keys on TERM anyway, and in some cases
> > (iwlagn) the driver will keep trying to reassociate internally
> 
> Seems unlikely, ITYM ipw?

Nope.  I saw this behavior with iwlagn (both 3945 and 4965) when I was
doing all that hidden stuff back in April with 2.6.27 kernels.  Might be
different in very recent kernels?

Dan



  reply	other threads:[~2009-07-13 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 11:43 nl80211 and wext interoperability Johannes Berg
2009-07-09 14:43 ` John W. Linville
2009-07-09 17:13 ` Pavel Roskin
2009-07-09 17:48   ` Johannes Berg
2009-07-13 17:55     ` Dan Williams
2009-07-09 17:53 ` Luis R. Rodriguez
2009-07-09 18:15   ` Johannes Berg
2009-07-13 17:53     ` Dan Williams
2009-07-13 17:54       ` Johannes Berg
2009-07-13 19:10         ` Dan Williams [this message]
2009-07-13 19:14           ` Johannes Berg
2009-07-13 20:52             ` 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=1247512206.4369.67.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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.