From: Vojtech P. <vo...@su...> - 2001-06-22 12:54:18
|
On Fri, Jun 22, 2001 at 01:41:02PM +0200, Ralf Ackermann wrote: > Hello, > > after reading input.txt in the kernel documentation my question is: > - Is there a way / interface to generate (feed into the kernel) > events into the kernel? > I mean - the opposite to /dev/input/eventX (that can be read) - > i would like to use an interface (e.g. a named pipe) that i can > feed data into (e.g. the bytes that normally arrive from a serially > attached device) so that they trigger events like a real device. > Background - that would permit to use a network attached input device by > just "tunneling" its data to the final destination. > It would also permit very easy simulation / test of devices. Before i try > myself - does that mechanism exist already? Which semantics / API does it > have? For complete functionality like this you'll need something ala evdev, but turned inside out. It hasn't been written yet, though I was planning it. You can also write() events to evdev, but that won't create the device, of course. -- Vojtech Pavlik SuSE Labs |