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@xxxxxxxxx> 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. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
