| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2007-05-03 | Input: force feedback - make sure effect is present before playing | Dmitry Torokhov | 1 | -1/+2 | |
| Make sure that requested effect id is not out of range for the device and that effect is present before requesting device to play it. Reported-by: Jan Kratochvil <[email protected]> Signed-off-by: Dmitry Torokhov <[email protected]> | |||||
| 2006-11-24 | Input: add to kernel-api docbook | Randy Dunlap | 1 | -2/+2 | |
| Add input subsystem to kernel-api docbook. Enhance some function and parameter comments. Signed-off-by: Randy Dunlap <[email protected]> Signed-off-by: Dmitry Torokhov <[email protected]> | |||||
| 2006-07-19 | Input: implement new force feedback interface | Anssi Hannula | 1 | -0/+367 | |
| Implement a new force feedback interface, in which all non-driver-specific operations are separated to a common module. This includes handling effect type validations, locking, etc. The effects are now file descriptor specific instead of the previous strange half-process half-fd specific behaviour. The effect memory of devices is not emptied if the root user opens and closes the device while another user is using effects. This is a minor change and most likely no force feedback aware programs are affected by this negatively. Otherwise the userspace interface is left unaltered. Signed-off-by: Anssi Hannula <[email protected]> Signed-off-by: Dmitry Torokhov <[email protected]> | |||||