At Mon, 18 Oct 2010 10:47:31 +0200, Corentin Chary wrote: > > On Mon, Oct 18, 2010 at 10:25 AM, Dmitry Torokhov > <[email protected]> wrote: > > On Mon, Oct 18, 2010 at 10:19:37AM +0200, Corentin Chary wrote: > >> On Mon, Oct 18, 2010 at 10:12 AM, Dmitry Torokhov > >> <[email protected]> wrote: > >> > On Sun, Oct 17, 2010 at 10:53:04PM -0600, Joey Lee wrote: > >> >> +static const struct key_entry acer_wmi_keymap[] = { > >> >> + {KE_KEY, 0x01, {KEY_WLAN} }, /* WiFi */ > >> >> + {KE_KEY, 0x12, {KEY_BLUETOOTH} }, /* BT */ > >> >> + {KE_KEY, 0x21, {KEY_PROG1} }, /* Backup */ > >> >> + {KE_KEY, 0x22, {KEY_PROG2} }, /* Aracade */ > >> >> + {KE_KEY, 0x23, {KEY_PROG3} }, /* P_Key */ > >> >> + {KE_KEY, 0x24, {KEY_PROG4} }, /* Social networking_Key */ > >> >> + {KE_KEY, 0x64, {KEY_SWITCHVIDEOMODE} }, /* Display Switch */ > >> >> + {KE_KEY, 0x82, {KEY_F22} }, /* Touch Pad On/Off */ > >> > > >> > We need to standardize this. Some people use F13/F14, here we have > >> > F22... > >> > > >> > >> The good thing with F* keys, is that they are already mapped in > >> X/Qt/SDL/etc.. > >> > >> But if we do, we could add KEY_TOUCHPADTOGGLE 0x1b8 > >> Then bind it to XF86XK_TouchpadToggle (what's the right way to do that > >> ? keymaps ?) > >> > > > > I wonder who the main consumers of such events will be... X applications > > or daemons that listen turn this into some DBUS signal... > > I guess xbindkeys and tools like qsynaptics should be able to consume > such events. > HAL also handled some touchpads things, but now that it is deprecated, who is > in > charge of doing that ?
There seems no standardization forseen, but which daemon (as of local user) is used depends on the desktop environment. For example, it's gnome-settings-daemon for GNOME. Takashi -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
