From: Larry Finger <Larry.Finger@lwfinger.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [RFC V2] b43: A patch for control of the radio LED using rfkill
Date: Thu, 18 Sep 2008 11:49:01 -0500 [thread overview]
Message-ID: <48D2867D.6010501@lwfinger.net> (raw)
In-Reply-To: <20080918162440.GL1583@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
>
> The problem is in the "should".
>
> Maybe something else than b43 (like firmware) changed the radio software
> rfkill bit, and it does not match what mac80211 and userland requested
> anymore.
>
> What you need to pass to rfkill_force_state() is what the radio is currently
> doing. So, the state you need to send to rfkill_force_state has to be based
> on the real state of the hardware's "soft switch bit".
The hardware does not have such a bit. Once it is initialized and
mac80211 sends it a packet, it will try to send it. That is true even
if the hardware switch is off. It just will not succeed.
> If the hardware "soft switch" bit is write-only, you have no choice but to
> use the mac80211 value like your V2 patch does, BTW.
Since we have only a read-only hardware switch bit, I think you are
saying that V2 is correct.
Larry
next prev parent reply other threads:[~2008-09-18 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 14:07 [RFC V2] b43: A patch for control of the radio LED using rfkill Larry Finger
2008-09-18 14:24 ` Henrique de Moraes Holschuh
2008-09-18 14:28 ` Ivo van Doorn
2008-09-18 14:48 ` Henrique de Moraes Holschuh
2008-09-18 15:17 ` Larry Finger
2008-09-18 16:24 ` Henrique de Moraes Holschuh
2008-09-18 16:49 ` Larry Finger [this message]
2008-09-18 17:20 ` Michael Buesch
2008-09-18 20:21 ` Henrique de Moraes Holschuh
2008-09-18 20:32 ` Henrique de Moraes Holschuh
2008-09-18 17:46 ` Michael Buesch
2008-09-18 20:24 ` Henrique de Moraes Holschuh
2008-09-18 17:14 ` Michael Buesch
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=48D2867D.6010501@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@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 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.