linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
	networkmanager-list@gnome.org, linux-wireless@vger.kernel.org,
	kde-hardware-devel@kde.org, dbus@lists.freedesktop.org,
	hal@lists.freedesktop.org
Subject: Re: [PATCH 32/33] input: add KEY_WIRELESS_CYCLE
Date: Thu, 3 Dec 2009 10:22:16 +0100	[thread overview]
Message-ID: <71cd59b00912030122n3d94236ajfa5e55c3b5a9efcd@mail.gmail.com> (raw)
In-Reply-To: <20091203085717.GO9121@core.coreip.homeip.net>

On Thu, Dec 3, 2009 at 9:57 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> 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.

Here it is.

Dear system infrastructure people,
Do you think a KEY_WIRELESS_CYCLE key would have any application ?

-- 
Corentin Chary
http://xf.iksaif.net

       reply	other threads:[~2009-12-03  9: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                   ` Corentin Chary [this message]
2009-12-03  9:43                     ` [PATCH 32/33] input: add KEY_WIRELESS_CYCLE Johannes Berg
2009-12-03 11:23                       ` [Kde-hardware-devel] " Will Stephenson
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=71cd59b00912030122n3d94236ajfa5e55c3b5a9efcd@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=dbus@lists.freedesktop.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hal@lists.freedesktop.org \
    --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).