From: Jonathan Bither <jonbither@gmail.com>
To: Valdis.Kletnieks@vt.edu, "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ArikX Nemtsov <arik@wizery.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting
Date: Fri, 20 Feb 2015 10:02:39 -0500 [thread overview]
Message-ID: <54E74C8F.9020606@gmail.com> (raw)
In-Reply-To: <36119.1424394185@turing-police.cc.vt.edu>
On 02/19/2015 08:03 PM, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
>> Wider community:
>>
>> anyone aware of any *need* in the kernel to know whether one is indoor or
>> not on a device running Linux other than wifi? Clearly it should be something
>> that might be of interest to at least other RF devices, so that is at least
>> one possibilty to consider already, but what else?
>
> I can think of a lot of reasons for the kernel to make indoor/outdoor
> status available to userspace, but am coming up empty why the kernel itself
> should care....
>
That made me try to think of the possible uses for such a variable but I
imagine that they can all be handled by userspace as well.
Powering down GPS chips for energy consumption.
Applying filters to cameras for fluorescent lights.
next prev parent reply other threads:[~2015-02-20 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:59 [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting Ilan Peer
2015-02-02 14:59 ` [PATCH v4 2/2] cfg80211: Schedule timeout for all CRDA calls Ilan Peer
2015-02-06 23:59 ` Luis R. Rodriguez
2015-02-06 23:58 ` [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting Luis R. Rodriguez
2015-02-08 9:10 ` Peer, Ilan
2015-02-10 20:00 ` Luis R. Rodriguez
2015-02-15 12:26 ` Peer, Ilan
2015-02-20 0:53 ` Luis R. Rodriguez
2015-02-20 1:03 ` Valdis.Kletnieks
2015-02-20 2:09 ` Luis R. Rodriguez
2015-02-20 15:02 ` Jonathan Bither [this message]
2015-02-20 15:57 ` Luis R. Rodriguez
2015-02-22 7:57 ` Peer, Ilan
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=54E74C8F.9020606@gmail.com \
--to=jonbither@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arik@wizery.com \
--cc=ilan.peer@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@suse.com \
/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).