[Vojtech Pavlik <vojtech@su...>]

On Wed, Feb 14, 2007 at 09:44:46AM -0500, Jon Smirl wrote:
> >Sending an IR signal involves things like setting the carrier frequency,
> >duty cycle, and then writing a stream of timing values.
> >I think that evdev in general is not the right interface for this.
> 
> This could be worked into the evdev support. lircd.conf would contain
> entries for the controls you wanted to send codes for. This info could
> be used to created an uinput/evdev entry for the control. If evdev
> supports pushing events, lircd could take the event and convert it to
> IR info and push it down into the lirc drivers.
> 
> We need Vojtech to tell us if we can push events into uinput.

You can. However, the event direction depends on the event type: EV_KEY
always goes from device to handler, EV_LED goes both ways. You'd have a
new event type for sending out IR events: This is different from
pressing a key. But it's trivial to add.

-- 
Vojtech Pavlik
Director SuSE Labs