On Thu, Dec 3, 2009 at 9:57 AM, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> 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@xxxxxxxxx> 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@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. >> >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
