Thread (33 messages) 33 messages, 6 authors, 2010-07-29

Re: Can I expect in-kernel decoding to work out of box?

From: Jon Smirl <hidden>
Date: 2010-07-28 17:04:11
Also in: linux-media

On Wed, Jul 28, 2010 at 11:56 AM, Mauro Carvalho Chehab
[off-list ref] wrote:
Em 28-07-2010 11:41, Jon Smirl escreveu:
quoted
It's possible to build a Linux IR decoder engine that can be loaded
with the old LIRC config files.
I think it is a good idea to have a decoder that works with such files anyway.
The recorder should use the Linux IR system to record the data. It
would confusing to mix the systems. Users need to be really sure that
the standard protocol decoders don't understand their protocol before
resorting to this. Any one in this situation should post their
recorded data so we can check for driver implementation errors.

An example: if you use irrecord on Sony remotes lirc always records
them in raw mode. The true problem here is that irrecord doesn't
understand that Sony remotes mix different flavors of the Sony
protocol on a single remote. This leads you to think that the Sony
protocol engine is broken when it really isn't. It's the irrecord tool
that is broken.  The kernel IR system will decode these remotes
correctly without resorting to raw mode.
There are some good reasons for that, as it would allow in-kernel support for
protocols that may have some patent restrictions on a few countries that allow
patents on software.
Are there any IR protocols less than 20 (or 17) years old? If they are
older than that the patents have expired. I expect IR use to decline
in the future, it will be replaced with RF4CE radio remotes.
We'll need to discuss the API requirements for such decoder, in order to load
the RC decoding code into it.

Cheers,
Mauro.


-- 
Jon Smirl
jonsmirl@gmail.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help