Yes, in kernel clean/smalls (encoding/)decoding engines abstracted by 
the input subsystem
are a good thing.
But you still need a way to send and received raw IR signal  to be able 
to send or
decode very out of spec signals like RC5 timing dependent  Philips 
service mode
codes. Or simply to decode / reverse engineer an IR protocol not already 
implemented

Best regards,
Emmanuel.

--

[ message continues ]

On Mon, Sep 29, 2008 at 6:18 PM, Emmanuel Fusté

I've been considering a sysfs interface for raw signals. Specialized
apps that can handle raw signal could use this interface. It's not
hard to add support for raw codes, maybe in the next pass. Something
like a "raw" attribute. Write ints to it and they get sent, read ints
from it to see what was received.




-- 
Jon Smirl
jonsmirl@gmail.com
--

[ message continues ]

Just one question,

Suppose I have non-standard remote, and I want to teach lirc to use it,
and I have general purpose receiver, how can I do this?

Best regards,

--

[ message continues ]

You need to write an app to use the sysfs interface for raw code. Or
you could write an in-kernel encoder/decoder and use the standard
interfaces. Or you could throw it away and spend $10 for a standard
one.


-- 
Jon Smirl
jonsmirl@gmail.com
--

[ message continues ]