From: Will Stephenson <wstephenson@kde.org>
To: kde-hardware-devel@kde.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Corentin Chary <corentin.chary@gmail.com>,
dbus@lists.freedesktop.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-wireless@vger.kernel.org, hal@lists.freedesktop.org,
linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
networkmanager-list@gnome.org, Len Brown <lenb@kernel.org>
Subject: Re: [Kde-hardware-devel] [PATCH 32/33] input: add KEY_WIRELESS_CYCLE
Date: Thu, 3 Dec 2009 12:23:04 +0100 [thread overview]
Message-ID: <200912031223.04419.wstephenson@kde.org> (raw)
In-Reply-To: <1259833412.12843.7.camel@johannes.local>
On Thursday 03 December 2009 10:43:32 Johannes Berg wrote:
> On Thu, 2009-12-03 at 10:22 +0100, Corentin Chary wrote:
> > Dear system infrastructure people,
> > Do you think a KEY_WIRELESS_CYCLE key would have any application ?
>
> Not really.
>
> The naming of the key ultimately will not matter one bit, because it'll
> be misnamed on most platforms anyway, unless we want to do DMI matching
> or something to name the key. And even then, if there's a wifi key but
> no bluetooth key, users may prefer to have the wifi key act as a cycle
> key instead.
>
> Therefore, this ought to all be policy in the rfkill daemon.
> rfkill-input will be going away as soon as somebody writes a simple
> daemon that allows doing such things, I really don't see us adding
> support for a cycle key to the kernel code, and for the userspace code
> it doesn't matter since users will configure it independent of the key
> code anyway.
This sounds reasonable to me, as the wireless guy in the KDE camp. I don't
want to have to handle these keypresses in a user session anyway - I prefer
that NetworkManager picks up on them and notifies the client of the state
change.
Will
next prev parent reply other threads:[~2009-12-03 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1259826317-18809-28-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-30-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-31-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-32-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-33-git-send-email-corentincj@iksaif.net>
[not found] ` <20091203075404.GK9121@core.coreip.homeip.net>
[not found] ` <71cd59b00912030012r2f45f474u37c494ad281230cb@mail.gmail.com>
[not found] ` <20091203082120.GL9121@core.coreip.homeip.net>
[not found] ` <71cd59b00912030051w6bf54abfv726f288c2eae1d33@mail.gmail.com>
[not found] ` <20091203085717.GO9121@core.coreip.homeip.net>
2009-12-03 9:22 ` [PATCH 32/33] input: add KEY_WIRELESS_CYCLE Corentin Chary
2009-12-03 9:43 ` Johannes Berg
2009-12-03 11:23 ` Will Stephenson [this message]
2009-12-03 15:01 ` Matthew Garrett
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=200912031223.04419.wstephenson@kde.org \
--to=wstephenson@kde.org \
--cc=corentin.chary@gmail.com \
--cc=dbus@lists.freedesktop.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hal@lists.freedesktop.org \
--cc=johannes@sipsolutions.net \
--cc=kde-hardware-devel@kde.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=networkmanager-list@gnome.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).