Hi Benjamin, On Fri, Jan 17, 2014 at 02:12:51PM -0500, Benjamin Tissoires wrote: > Evemu [1] uses uinput to replay devices traces it has recorded. However, > the way evemu uses uinput is slightly different from how uinput is > supposed to be used. > Evemu relies on libevdev, which creates the device node through uinput. > It then injects events through the input device node directly (and it > completely skips the uinput node). > > Currently, libevdev relies on an heuristic to guess which input node was > created. The problem is that is heuristic is subjected to races between > different uinput devices or even with physical devices. Having a way > to retrieve the sysfs path allows us to find the event node without > having to rely on this heuristic. I have been thinking about it and I think that providing tight coupling between uinput and resulting event device is wrong thing to do. We do allow sending input events through uinput interface and I think evemu should be using it, instead of going halfway through uinput and halfway though evdev. Replaying though uinput would actually be more correct as it would involve the same code paths throgugh input core as with using real devices (see input_event() vs. input_inject_event() that is used by input handlers). Thanks. -- Dmitry -- 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
