From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 32/33] input: add KEY_WIRELESS_CYCLE
Date: Thu, 3 Dec 2009 00:57:17 -0800 [thread overview]
Message-ID: <20091203085717.GO9121@core.coreip.homeip.net> (raw)
In-Reply-To: <71cd59b00912030051w6bf54abfv726f288c2eae1d33@mail.gmail.com>
On Thu, Dec 03, 2009 at 09:51:59AM +0100, Corentin Chary wrote:
> On Thu, Dec 3, 2009 at 9:21 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Thu, Dec 03, 2009 at 09:12:52AM +0100, Corentin Chary wrote:
> >> On Thu, Dec 3, 2009 at 8:54 AM, Dmitry Torokhov
> >> <dmitry.torokhov@gmail.com> wrote:
> >> > On Thu, Dec 03, 2009 at 08:45:16AM +0100, Corentin Chary wrote:
> >> >> This keycode could be used in a lot of platform specific drivers.
> >> >> For example, on Asus laptops, Fn+F2 allow to cycle trought wireless
> >> >> drivers (bt/wl: off/off, on/off, off/on, on/on).
> >> >>
> >> >> Currently, these key are mapped to KEY_WLAN, and KEY_BLUETOOTH/KEY_WIMAX
> >> >> are rarely used.
> >> >>
> >> >
> >> > Is there any application support for such cycling? IOW does anyone cares
> >> > to do such cycling?
> >>
> >> On Asus laptops (both asus and eeepc) the Fn+F2 key cycle
> >> (bluetooth/wlan: on/on, on/off, off/on, off/off) on windows.
> >> On Linux, it only produces a KEY_WLAN keycode.
> >>
> >
> > I understand this. I guess the question is whether people working on
> > system infrastructure (dbus, Networkmanager, etc) care about having such
> > functionality on Linux? The reason I am asking is that we added all
> > KEY_WIMAX and so on defines but I am not usre if anyone wants them.
>
> KEY_WIMAX may not be used a lot because there is not a lot of device
> with such a key,
> I think this is not the case for KEY_WIRELESS_CYCLE.
>
> The bad thing is that we will need to patch X11 (and Qt, for
> kde/solid) to make it works.
>
> Maybe we should Cc dbus/network manager/solid/linux-wireless ?
>
That would be a good idea.
--
Dmitry
next prev parent reply other threads:[~2009-12-03 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1259826317-18809-1-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-2-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-3-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-4-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-5-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-6-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-7-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-8-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-9-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-10-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-11-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-12-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-13-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-14-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-15-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-16-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-17-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-18-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-19-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-20-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-21-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-22-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-23-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-24-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-25-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-26-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-27-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-28-git-send-email-corentincj@iksaif.net>
[not found] ` <1259826317-18809-29-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>
2009-12-03 7:45 ` [PATCH 32/33] input: add KEY_WIRELESS_CYCLE Corentin Chary
2009-12-03 7:54 ` Dmitry Torokhov
2009-12-03 8:12 ` Corentin Chary
2009-12-03 8:21 ` Dmitry Torokhov
2009-12-03 8:51 ` Corentin Chary
2009-12-03 8:57 ` Dmitry Torokhov [this message]
2009-12-03 9:22 ` Corentin Chary
2009-12-03 9:43 ` Johannes Berg
[not found] ` <1259833412.12843.7.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-12-03 11:23 ` [Kde-hardware-devel] " Will Stephenson
2009-12-03 15:01 ` Matthew Garrett
2009-12-06 6:58 ` Andrey Rahmatullin
2009-12-06 7:17 ` Dmitry Torokhov
2009-12-06 8:21 ` Corentin Chary
2009-12-06 14:54 ` Matthew Garrett
2009-12-07 11:47 ` Henrique de Moraes Holschuh
2009-12-07 12:55 ` Matthew Garrett
2009-12-07 13:23 ` Henrique de Moraes Holschuh
2009-12-07 14:20 ` Matthew Garrett
2009-12-07 17:02 ` Henrique de Moraes Holschuh
2009-12-03 10:54 ` Henrique de Moraes Holschuh
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=20091203085717.GO9121@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).