On Sun, Jan 17, 2016 at 2:27 PM, Manuel Reimer <Manuel.Spam@xxxxxxxxxxxxxx> wrote: > Hello, > > I have an existing uinput driver, which itself sits on an open device with a > blocking read(), waiting for events to come in. Every event is translated to > a key code and then sent to uinput. > > My next step would be to pass through force feedback information, but I > don't really understand how I should do this. Concerning this, the following may give you an example how to read incoming FF events on uinput: https://github.com/xboxdrv/xboxdrv/blob/8e9fb6b40df568d4e4af63e80518366ee4aa5fd3/src/linux_uinput.cpp#L341 A good while ago I started working on FF support for the uinput user-space library libsuinput, (and also for python-uinput,) but I have to clean up some things before I can merge it to: https://github.com/xboxdrv/xboxdrv/blob/8e9fb6b40df568d4e4af63e80518366ee4aa5fd3/src/linux_uinput.cpp#L341 Thanks, Elias -- 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
