Re: [PATCH 32/33] input: add KEY_WIRELESS_CYCLE

[Corentin Chary <corentin.chary@gmail.com>]

On Sun, Dec 6, 2009 at 8:17 AM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Sun, Dec 06, 2009 at 11:58:29AM +0500, Andrey Rahmatullin wrote:
>> On Thu, Dec 03, 2009 at 09:12:52AM +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.
>> Default eee901's Xandros cycles and even shows an OSD with BT and WLAN
>> state images.
>>
>
> You are describing the visible result. Whether it is done as a custom
> policy to KEY_WLAN presses or utilizes a separate key definition - is
> not known.
Old xandros builds use the acpi event.
New builds have switched to eeepc-laptop (based on my 2.6.30
backport), so they may use an input event (KEY_WLAN).

> Anyway, we got the response form wireless developers and infrastructure
> people and thyy do not care about having a new defintion so I guess that
> settles it.
Yep

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