On Sun, 2010-04-18 at 13:19 -0700, Dmitry Torokhov wrote: <snip> > > > Hmm, I am curious why suspend and resume is not necessary for this > > > device... Are you relying on the USB core to tear down and re-create the > > > device? Then you may lose user-applied settings (like changed keymap). > > > > How could I test that? > > Change the keymap (with keyfuzz or something similar), suspend. resume and see > if the mapping persisted. Tried using udev's keymap tool on it, but the default get function doesn't give me any output. Am I supposed to implement get/setkeycode myself for this to work, or should the default input functions work? If the latter, is there anything missing in the driver for me to call to enable that? Trying to set a keycode says that the "EVIOCSKEYCODE" ioctl returns EINVAL. Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
