public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: on radio_enabled
Date: Fri, 24 Apr 2009 17:10:47 +0300	[thread overview]
Message-ID: <874oweb0rc.fsf@litku.valot.fi> (raw)
In-Reply-To: <1240568807.18031.34.camel@johannes.local> (Johannes Berg's message of "Fri\, 24 Apr 2009 12\:26\:47 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> I wonder where the use case for faster scanning is

Basically the situation where the device is not connected to any AP but
is periodidally trying to find one, for example by scanning every five
minutes. In that case every mW we can save in scanning improves use
times.

> but I guess the slow SPI bus really does make for a long delay in
> initialising due to firmware upload.

Exactly.

> I have no trouble with implementing it this way, and userspace can
> still set the interfaces down when it wishes to do that, while we can
> save a lot of power when userspace doesn't do it that way.

Yes.

> Now, what happens with "iwconfig wlan0 txpower off"? I can't figure out
> that one. Should it be completely equivalent to rfkill, regardless of
> what rfkill ends up doing?

In my opinion should be equivalent to rfkill. NB. I haven't properly
thought about this and I know nothing about rfkill, fortunately :)

-- 
Kalle Valo

      reply	other threads:[~2009-04-24 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 22:39 on radio_enabled Johannes Berg
2009-04-22 22:46 ` Gábor Stefanik
2009-04-24  6:24 ` Kalle Valo
2009-04-24 10:26   ` Johannes Berg
2009-04-24 14:10     ` Kalle Valo [this message]

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=874oweb0rc.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox