linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
	Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] rtl8187: Implement rfkill support
Date: Tue, 25 Aug 2009 02:51:27 +0000 (GMT)	[thread overview]
Message-ID: <622090.22128.qm@web23106.mail.ird.yahoo.com> (raw)
In-Reply-To: <4A933E87.7030600@lwfinger.net>

--- On Tue, 25/8/09, Larry Finger <Larry.Finger@lwfinger.net> wrote:

> > [PATCH] rtl8187: fix circular locking
> (rtl8187_stop/rtl8187_work)
> 
> This patch fixes the problem. You can add a Tested-by to
> it.

Hmm, I am still wondering about why NM insists on if up'ing the device. I read bits of things and apparently hal is supposed to know the device is rfkill'ed and let NM know. But lshal is not listing the device as having an killswitch. I don't know how hal is supposed to work out that info though. 

also I noted that /sys/class/rfkill_backport/rfkill0/state goes from 1 to 2 when I slide the switch to the 'off' position. Some says it should be 0?
Don't know if hal is affected by its being rfkill_backport (compat-wireless) rather than rfkill (stock vendor kernel). well, it should look there if it isn't :-).

It looks like it is a hal problem...


      


  reply	other threads:[~2009-08-25  2:57 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 [this message]
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=622090.22128.qm@web23106.mail.ird.yahoo.com \
    --to=htl10@users.sourceforge.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --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).