Re: Fwd: [linux-usb-devel] USB IR receivers and evdev

[Vojtech P. <vo...@su...>]

On Wed, Feb 14, 2007 at 11:27:44AM -0500, Jon Smirl wrote:

> You need something like this:
> 
> lircd opens /dev/uinput once for each remote control. This creates the
> corresponding /dev/input/event* nodes.
> 
> Remote gets clicked, lircd catches event and passes it to uinput. User
> app can read events from the /dev/input/event* nodes
> 
> Now user app wants to generate an event. User app writes it to the
> appropriate /dev/input/event* node.

That's fine as long as it's EV_IR_SEND event type, which can be
trivially added. EV_KEY will not work here, as EV_KEY doesn't get passed
up, since it's not possible to physically press a key on the remote by
software action.

The keys and the transmit ability will have to be treated as different
event types, but that's it.

> Does this node know it was created
> by /dev/uinput Will the event written to /dev/input/event* then be
> readable on the corresponding /dev/uinput handle?

The kernel knows it, and it'll pass it to the uinput for reading by the
appropriate process/handle.

-- 
Vojtech Pavlik
Director SuSE Labs