All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>,
	htl10@users.sourceforge.net,
	Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] rtl8187: Implement rfkill support
Date: Wed, 26 Aug 2009 07:45:52 -0500	[thread overview]
Message-ID: <4A952E80.4040306@lwfinger.net> (raw)
In-Reply-To: <1251277063.10667.10.camel@johannes.local>

Johannes Berg wrote:
> On Wed, 2009-08-26 at 03:43 +0100, Hin-Tak Leung wrote:
> 
>> The rfkill event hard just goes 1 and 0 whenever I slide the switch,
>> regardless of what NM does . e.g. NM set to disable networking has no
>> effect on the 1/0 switch (it happens just depending on the slide
>> switch and nothing else), and nothing changes when NM noticed
>> rfkill'ed if down & decided to if'up and reassociate.
> 
> Right, I just wanted to make sure the switch could be correctly read
> while the interface is down.
> 
>> Basically the rfkill event state just depends on the slide switch,
>> regardless of NM (if it is set to enable wireless networking, it just
>> if up the device again; if it is set to disable, it just stayed
>> disable & the device stay down, but the event state continues to
>> respond to the slide switch).
> 
> Ok. But this isn't making a lot of sense to me, since cfg80211 should
> refuse to UP the device when it's rfkilled.
> 
> Or wait ... are you using compat-wireless?

Yes he is.


  reply	other threads:[~2009-08-26 12:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22  3:38 [RFC/RFT] rtl8187: Implement rfkill support Herton Ronaldo Krzesinski
2009-08-22 17:12 ` Larry Finger
2009-08-22 21:59 ` Hin-Tak Leung
2009-08-23 19:38   ` Hin-Tak Leung
2009-08-24 18:10     ` Herton Ronaldo Krzesinski
2009-08-24 21:03       ` Hin-Tak Leung
2009-08-24  1:46 ` Larry Finger
2009-08-24 18:03   ` Herton Ronaldo Krzesinski
2009-08-25  1:29     ` Larry Finger
2009-08-25  2:51       ` Hin-Tak Leung
2009-08-25  3:36         ` Larry Finger
2009-08-25  6:51           ` Hin-Tak Leung
2009-08-25  9:27             ` Johannes Berg
2009-08-26  2:43               ` Hin-Tak Leung
2009-08-26  8:57                 ` Johannes Berg
2009-08-26 12:45                   ` Larry Finger [this message]
2009-08-26 13:33                   ` Hin-Tak Leung
2009-08-26 14:34                     ` Johannes Berg
2009-08-26 15:07                       ` Hin-Tak Leung
2009-08-26 16:57                         ` Herton Ronaldo Krzesinski
2009-08-26 16:29                       ` Hin-Tak Leung
2009-08-26 20:33                       ` Luis R. Rodriguez
2009-08-26 22:06                         ` Luis R. Rodriguez
2009-08-26 22:12                           ` Johannes Berg
2009-08-26 22:26                             ` Luis R. Rodriguez
2009-08-26 22:30                               ` Johannes Berg
2009-08-26 22:46                                 ` Luis R. Rodriguez

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=4A952E80.4040306@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=hintak.leung@gmail.com \
    --cc=htl10@users.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --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.