linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Julian Calaby" <julian.calaby@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Matthew Garrett" <mjg59@srcf.ucam.org>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	hmh@hmh.eng.br
Subject: Re: [RFC] b43: rework rfkill code
Date: Thu, 11 Dec 2008 02:27:25 +0100	[thread overview]
Message-ID: <200812110227.26909.mb@bu3sch.de> (raw)
In-Reply-To: <646765f40812101632u76847935l2405482aabe1c1f8@mail.gmail.com>

On Thursday 11 December 2008 01:32:37 Julian Calaby wrote:
> On Thu, Dec 11, 2008 at 02:29, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Wed, 2008-12-10 at 15:09 +0000, Matthew Garrett wrote:
> >
> >> The final change is that I removed the code for changing the wireless
> >> state in response to the txpower configuration in mac80211. Right now, I
> >> can't see any way for this to work correctly - if the user disables the
> >> radio via rfkill, mac80211 doesn't flag the radio as disabled. As a
> >> result, the next time the configuration callback is called, b43
> >> reenables the radio again, even though the user has explicitly disabled
> >> it. I don't think any of the other drivers handle this case, so I'm not
> >> really sure what the best way to handle this in future is. The current
> >> situation certainly seems broken.
> >
> > We're going to have to integrate rfkill with mac80211, but nobody cares.
> 
> What strikes me, watching this from the outside - is that rfkill and
> power saving seem to be doing essentially the same thing: temporarily
> powering down the radio / card.

I think it's essentially a different thing.
rfkill means -> turn off the radio; no matter what.
PS means -> turn off the radio for whatever amount of microseconds and periodically
wake up to see what's up.
PS-core also takes place in the firmware of the device, where rfkill is a much higher layer thing.

-- 
Greetings, Michael.

  reply	other threads:[~2008-12-11  1:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 15:09 [RFC] b43: rework rfkill code Matthew Garrett
2008-12-10 15:29 ` Johannes Berg
2008-12-10 16:15   ` Ivo van Doorn
2008-12-10 16:51   ` Marcel Holtmann
2008-12-10 17:18     ` Johannes Berg
2008-12-10 17:23       ` Johannes Berg
2008-12-10 17:28         ` Johannes Berg
2008-12-10 21:33           ` Henrique de Moraes Holschuh
2008-12-10 21:42             ` Michael Buesch
2008-12-10 17:31         ` Michael Buesch
2008-12-10 17:37           ` Johannes Berg
2008-12-10 17:51             ` Matthew Garrett
2008-12-10 18:04               ` Michael Buesch
2008-12-10 18:05               ` Johannes Berg
2008-12-10 18:09                 ` Matthew Garrett
2008-12-10 18:29                 ` Dan Williams
2008-12-10 18:33                   ` Johannes Berg
2008-12-10 18:59                     ` Dan Williams
2008-12-10 20:07                   ` Michael Buesch
2009-03-29 18:19     ` Johannes Berg
2008-12-11  0:32   ` Julian Calaby
2008-12-11  1:27     ` Michael Buesch [this message]
2008-12-11 13:28       ` Kalle Valo
2008-12-10 15:48 ` Michael Buesch
2008-12-10 16:12   ` Matthew Garrett
2008-12-11 16:55 ` Larry Finger
2008-12-12  4:28 ` Larry Finger
2008-12-17 15:48   ` John W. Linville

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=200812110227.26909.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=hmh@hmh.eng.br \
    --cc=johannes@sipsolutions.net \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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).