From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
To: "Hin-Tak Leung" <hintak.leung@gmail.com>
Cc: linux-wireless@vger.kernel.org, Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [RFC/RFT] rtl8187: Implement rfkill support
Date: Mon, 24 Aug 2009 15:10:10 -0300 [thread overview]
Message-ID: <200908241510.10968.herton@mandriva.com.br> (raw)
In-Reply-To: <3ace41890908231238h32b85839qe74bce2852103402@mail.gmail.com>
Em Dom 23 Ago 2009, às 16:38:43, Hin-Tak Leung escreveu:
> On Sat, Aug 22, 2009 at 10:59 PM, Hin-Tak Leung<hintak.leung@gmail.com> wrote:
> > On Sat, Aug 22, 2009 at 4:38 AM, Herton Ronaldo
> > Krzesinski<herton@mandriva.com.br> wrote:
> >> This change implements rfkill support for RTL8187B and RTL8187L devices,
> >> using new cfg80211 rfkill API.
> >>
> >> Signed-off-by: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
> >
> > Tested-by: Hin-Tak Leung <htl10@users.sourceforge.net>
> >
> > Neat!
> >
> > I ran a ping to the router while flicking the switch on and off, and
> > have 'ping: sendmsg: Network is unreachable' in the middle. dmesg also
> > shows
>
> It appears that I wrote prematurely - flicking the switch with the
> patch seems to just do the equivalent of ifconfig down.
Yes, the equivalent of ifconfig down is what cfg80211 rfkill does in this case.
> (before the patch, the switch has no effect). However, NetworkManager
> soon notices the interface going down and ifup it again. So I have
> simply got a 30s to 1 minute disruption in connectivity.
This is strange, may be NetworkManager does something extra and for some reason
manages to wake up the interface again? I thought it would be unable to "if up"
the interface since -ERFKILL should be returned to it when switch is off...
>
> Is this intentional? I thought it is supposed to actually switch off
> the hardware, or is this how the code supposed to work?
> Maybe some component needs to let NM knows not to reenanble the device.
About taking interface down, thats expected, but I don't know about
NetworkManager, I was expecting it to be unable to "if up" the interface again.
>
> Hin-Tak
>
--
[]'s
Herton
next prev parent reply other threads:[~2009-08-24 18:10 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 [this message]
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
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=200908241510.10968.herton@mandriva.com.br \
--to=herton@mandriva.com.br \
--cc=Larry.Finger@lwfinger.net \
--cc=hintak.leung@gmail.com \
--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 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).