On Mon, 28 May 2007, Dmitry Torokhov wrote: > Documentation/input/input-programming.txt gives some pointers. It is outdated, and incomplete. > > On that topic, am I to send SYNC events between key-press and key-release > > events? > > Yes. The application is allowed to "accumulate" input events until it gets > EV_SYN/SYN_REPORT so if you don't send sync in-between some applications > may not see a button press. Ok. Done that. > > Just after a key-press+key release event? Or not at all for a > > EV_KEY ? And exactly what should go in the hardware port descriptor? I used > > module name/input device number relative to the module. > > Are you talking about "phys"? Then it is supposed to have an unique path > to the input device. For devices on BUS_HOST module name + relative input > device numbers seems to be the best choice. Ok. Done that. Thanks. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - 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
