On Wed, 16 May 2007, Robert Marquardt wrote: > > Anyway, what would be your proposal here? Currently the output reports > > (for changing the keyboard LEDs, for example) are being submitted as > > soon as the corresponding input event occurs (on different keyboard), > > which makes sense. Could you be more elaborate on what are the exact > > drawbacks you see here, and what would your proposal be? (postponing > > it into workqueue? why?). > The basic problem is the difference between CAPS LOCK event and CAPS > LOCK state. The state may be in user space only. Windows even has it on
We have the LEDs states per-terminal. I do not think that changing this is going to happen. > > If you think so, please raise this on linux-input mailing list (and CC at > > least me and Dmitry). > When i find time (yet another list to subscribe to). You don't have to be subscribed to post into this mailinglist. Thanks, -- Jiri Kosina ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
